* git-svn mergeinfo
@ 2012-09-11 12:01 Brice Goglin
0 siblings, 0 replies; only message in thread
From: Brice Goglin @ 2012-09-11 12:01 UTC (permalink / raw)
To: git
Hello,
I am using git 1.7.10.4 from Debian. I just tried svn.pushmergeinfo and
it seems to have worked fine, great.
Now I am trying to understand what the doc says about this:
"Currently, this can only be done when dcommitting non-fast-forward
merges where all parents but the first have already been pushed into SVN."
"all parents but the first have already been pushed into SVN" means that
merging A into B requires to dcommit in A first, right?
"non-fast-forward" means that both branches got some commits since the
last merge, right?
Could we add an example after the above doc sentence? Something like
"For instance, if merging SVN branch B into A, make sure you dcommit A
first, and check that both A and B got new commits since the last merge
(or since B was created from A)".
Brice
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-09-11 12:01 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-09-11 12:01 git-svn mergeinfo Brice Goglin
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.