Eric Wong <normalperson@xxxxxxxx> writes:
> I've been considering something along those lines. I'm interested in
> renaming the current 'commit' command to something else (it still has
> its uses), but I haven't figured out what to call it...
I think this would be a sensible change and will help new users get
started with git-svn.
> Also, something that can wrap (git commit && git svn dcommit) into one
> step would be nice.
For my workflow, that wouldn't be all that useful. I find that I
accumulate a few commits locally and then send them all to svn. For
this workflow, what would be useful is if dcommit could understand a
command like:
git svn dcommit remotes/git-svn..HEAD~2
Sometimes I realize I should have sent a stack of commits to svn, but
now have some newer commits that aren't quite ready on the head of my
branch.
While the workaround is easy (create a new branch and dcommit from
it), I think there is a usability argument in that when one
sees an example like dcommit foo..bar, one expects all
the other magic to work. I feel for this and accidentally committed a
few commits I didn't want to send. If nothing else, perhaps git-svn
could error out and say, "hey, I don't do that".
+ seth
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html