From: Eric Wong <normalperson@yhbt.net>
To: Seth Falcon <sethfalcon@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/3] git-svn: documentation updates
Date: Sat, 2 Dec 2006 17:49:42 -0800 [thread overview]
Message-ID: <20061203014942.GF1369@localdomain> (raw)
In-Reply-To: <m2wt5es0r3.fsf@ziti.fhcrc.org>
Seth Falcon <sethfalcon@gmail.com> wrote:
> Eric Wong <normalperson@yhbt.net> 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".
Aded to my ever-growing git-svn todo list. Patches welcome :)
--
prev parent reply other threads:[~2006-12-03 1:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 2:51 [PATCH 1/3] git-svn: color support for the log command Eric Wong
2006-11-29 2:51 ` [PATCH 2/3] git-svn: documentation updates Eric Wong
2006-11-29 2:51 ` [PATCH 3/3] git-svn: fix multi-init Eric Wong
2006-11-29 7:29 ` [PATCH 2/3] git-svn: documentation updates Steven Grimm
2006-11-29 8:54 ` Eric Wong
2006-11-29 12:35 ` Pazu
2006-12-03 1:39 ` Eric Wong
2006-12-03 1:52 ` Junio C Hamano
2006-12-03 2:12 ` Eric Wong
2006-11-29 15:58 ` Seth Falcon
2006-12-03 1:49 ` Eric Wong [this message]
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=20061203014942.GF1369@localdomain \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=sethfalcon@gmail.com \
/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).