From: Shawn Pearce <spearce@spearce.org>
To: Seth Falcon <sethfalcon@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-svn bug?
Date: Wed, 15 Nov 2006 17:37:10 -0500 [thread overview]
Message-ID: <20061115223709.GG24861@spearce.org> (raw)
In-Reply-To: <m2psbocpbo.fsf@ziti.local>
Seth Falcon <sethfalcon@gmail.com> wrote:
> I always send commits as:
>
> git-svn dcommit remotes/git-svn..master
>
> Possibly replacing master with whatever git branch I'm working on.
Or just:
git-svn dcommit remotes/git-svn..
to send the current branch.
> One nice thing about this approach is that you can sort of preview the
> commit as:
>
> git diff remotes/git-svn..master
Or see the log and patch of each commit on the current branch:
git log -p remotes/git-svn..
--
next prev parent reply other threads:[~2006-11-15 22:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 21:05 git-svn bug? Troy Telford
2006-11-15 21:43 ` Junio C Hamano
2006-11-15 22:55 ` Troy Telford
2006-11-17 8:55 ` Eric Wong
2006-11-17 21:17 ` Troy Telford
2006-11-19 16:52 ` Eric Wong
2006-11-15 22:33 ` Seth Falcon
2006-11-15 22:37 ` Shawn Pearce [this message]
2006-11-16 15:32 ` Seth Falcon
2006-11-15 23:09 ` Troy Telford
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=20061115223709.GG24861@spearce.org \
--to=spearce@spearce.org \
--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).