From: Eric Wong <normalperson@yhbt.net>
To: Hin-Tak Leung <htl10@users.sourceforge.net>
Cc: stoklund@2pi.dk, fabian.schmied@gmail.com, git@vger.kernel.org,
sam@vilain.net, stevenrwalter@gmail.com, waste.manager@gmx.de,
amyrick@apple.com
Subject: Re: differences between old clone and new Re: git-svn performance
Date: Thu, 30 Oct 2014 00:21:36 +0000 [thread overview]
Message-ID: <20141030002136.GA31920@dcvr.yhbt.net> (raw)
In-Reply-To: <1414540742.41763.YahooMailBasic@web172305.mail.ir2.yahoo.com>
Hin-Tak Leung <htl10@users.sourceforge.net> wrote:
> On Tue, 28/10/14, Eric Wong <normalperson@yhbt.net> wrote:
>
> > So both merges
> are correct, but we lose one, and gain one?
> I'll try to check more closely tomorrow.
> Can you point out
> the exact revisions in the
> R repo? Thanks.
>
>
> The missing merge on branch "R-2-14-branch" is:
>
> commit 93af4d4cc3a5e0039944dd4e340d26995be8a252
> Merge: 121990f 6ff1b87
> Author: ripley <ripley@00db46b3-68df-0310-9c12-caf00c1e9a41>
> Date: Wed Feb 22 13:45:34 2012 +0000
>
> port r58453 from trunk
>
> git-svn-id: https://svn.r-project.org/R/branches/R-2-14-branch@58454 00db46b3-68df-0310-9c12-caf00c1e9a41
I'm curious if you can tell me which version of git-svn you used to get
that as a merge commit. git-svn mergeinfo handling has changed
(hopefully improved) over the years, so some differences in history
can be (unfortunately) expected, I think.
I cannot reproduce your original merge on Junio's current master. Using
Junio's master[1] without any recent git-svn changes, a partial clone
doing:
git svn clone -s -r52000:58600 svn+ssh://127.0.0.1/path/to/my/R-mirror
...causes the merges in r58454 to be ignored as cherry-picks, too.
I suspect it's correct for git-svn to ignore those as cherry-picks
nowadays.
Here's a snippet of what I see from the above command:
----------------------------------8<-----------------------------------
r58452 = ebf3a1ca312ca7cc03dc2387d86491a0cdc95bad (refs/remotes/origin/trunk)
M src/library/base/man/Primitive.Rd
M src/main/names.c
M doc/NEWS.Rd
r58453 = 05b55eee9e6bed628873d34261e54c70f87a3736 (refs/remotes/origin/trunk)
M doc/NEWS.Rd
M src/library/base/man/Primitive.Rd
M src/main/names.c
W:svn cherry-pick ignored (/branches/R-2-12-branch:52939,54476,55265) - missing 492 commit(s) (eg df9d875de507ac51932c0ed980392e8262f98b31)
W:svn cherry-pick ignored (/branches/R-2-13-branch:55265,55432) - missing 231 commit(s) (eg cad052d416d9b8a9dfbfb2ae7bf85c39306c67bb)
W:svn cherry-pick ignored (/trunk:57183,57204-57205,57242,57259,57314,57316,57321,57370,57411,57428,57430,57432,57438,57440,57484,57489-57490,57579,57589,57604,57614-57618,57625,57679,57681,57687,57738,57741,57744-57745,57747,57752,57758,57761,57763,57765,57767,57769,57771,57790,57793,57803,57812,57814,57816,57826-57827,57836,57840-57841,57844,57846,57851,57853,57856,57861-57862,57867,57880,57884,57890,57893,57895,57900,57904,57908,57913,57920,57936,57939-57941,57950,57952,57959,57964,57970,57975,57977,57981,57987,58006,58008,58037,58039,58042,58047,58052,58056,58058,58066-58067,58082,58084,58089,58094,58098,58100,58107,58126,58129,58135,58142,58161,58178,58182,58187,58195,58204,58213,58217,58221,58225,58228,58232,58234,58239,58248,58253,58265,58269,58272,58274,58276,58278,58282,58284,58288,58294,58296,58305,58312,58314,58318,58324,58326,58328,58332,58334,58340,58346,58348,58353,58355,58357,58359,58361,58373,58378,58381,58386,58388,58392,58395,58397,58405,58412,58415,58429,58435,58437,58439,58453) - missing 716 commit(s) (eg e9ccca5db27696ed8faa4427ec4110ddf230d141)
r58454 = 96d6087a494bb7da6d90f02e8bd36833eaad2067 (refs/remotes/origin/R-2-14-branch)
M doc/manual/R-exts.texi
M doc/NEWS.Rd
M src/library/tools/R/check.R
r58455 = 742cbc791fa6760d5dfb4c4ea1e032d32e9e87c9 (refs/remotes/origin/trunk)
----------------------------------8<-----------------------------------
[1] - fbecd99 Update draft release notes to 2.2
next prev parent reply other threads:[~2014-10-30 0:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 23:26 Anomaly with the new code - Re: git-svn performance Hin-Tak Leung
2014-10-28 5:40 ` differences between old clone and new " Hin-Tak Leung
2014-10-28 7:41 ` Eric Wong
2014-10-28 23:59 ` Hin-Tak Leung
2014-10-30 0:21 ` Eric Wong [this message]
2014-10-30 0:55 ` Hin-Tak Leung
2014-10-30 23:08 ` Eric Wong
2014-10-28 23:33 ` Regression and failure to clone/fetch with new code " Hin-Tak Leung
2014-10-29 19:23 ` Eric Wong
2014-10-30 0:06 ` Hin-Tak Leung
2014-10-30 0:28 ` Eric Wong
2014-10-30 2:35 ` Hin-Tak Leung
2014-10-30 8:46 ` Eric Wong
2014-10-28 7:45 ` Anomaly with the new code - " Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141030002136.GA31920@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=amyrick@apple.com \
--cc=fabian.schmied@gmail.com \
--cc=git@vger.kernel.org \
--cc=htl10@users.sourceforge.net \
--cc=sam@vilain.net \
--cc=stevenrwalter@gmail.com \
--cc=stoklund@2pi.dk \
--cc=waste.manager@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).