Jon Seymour [off-list ref] writes:
quoted
+Originally, 'git svn' recommended that developers pulled or merged from
+the 'git svn' branch. This was because the author favored `git svn set-tree B`
+to commit a single head rather than the `git svn set-tree A..B` notation to
+commit multiple commits. Use of 'git pull' or 'git merge' with `git svn set-tree A...B`
A...B -> A..B
Will fix in next iteration, assuming Junio and Eric are otherwise
happy with the update.
I don't have an opinion on the latter half of the patch that is primarily
about the rationale given by "the author", i.e. Eric ;-), but the
description of dcommit subcommand itself certainly looks simpler and more
readble to me.
Thanks.
On Thu, May 17, 2012 at 8:49 AM, Junio C Hamano [off-list ref] wrote:
Jon Seymour [off-list ref] writes:
quoted
quoted
+Originally, 'git svn' recommended that developers pulled or merged from
+the 'git svn' branch. This was because the author favored `git svn set-tree B`
+to commit a single head rather than the `git svn set-tree A..B` notation to
+commit multiple commits. Use of 'git pull' or 'git merge' with `git svn set-tree A...B`
A...B -> A..B
Will fix in next iteration, assuming Junio and Eric are otherwise
happy with the update.
I don't have an opinion on the latter half of the patch that is primarily
about the rationale given by "the author", i.e. Eric ;-), but the
description of dcommit subcommand itself certainly looks simpler and more
readble to me.
Thanks.
Ok, I'll fix the ... issue mentioned above and (also some trailing
whitespace) once Eric has given his feedback or acknowledgement.
jon.
Jon Seymour [off-list ref] wrote:
Ok, I'll fix the ... issue mentioned above and (also some trailing
whitespace) once Eric has given his feedback or acknowledgement.
Looks good to me. Can you be sure to wrap changes at <80 chars
(I like big fonts :D)