From: "Lee Marlow" <lee.marlow@gmail.com>
To: "Miklos Vajna" <vmiklos@frugalware.org>
Cc: git@vger.kernel.org
Subject: Re: Showing changes about to be commited via git svn dcommit
Date: Mon, 28 Jul 2008 18:32:36 -0600 [thread overview]
Message-ID: <7968d7490807281732x27a3987cka664ae64351f6751@mail.gmail.com> (raw)
In-Reply-To: <20080728235326.GQ32057@genesis.frugalware.org>
Works perfectly and makes sense to boot! Thanks, Miklos
-Lee
On Mon, Jul 28, 2008 at 5:53 PM, Miklos Vajna <vmiklos@frugalware.org> wrote:
> On Mon, Jul 28, 2008 at 04:54:19PM -0600, Lee Marlow <lee.marlow@gmail.com> wrote:
>> $> git svn dcommit --dry-run | grep -E '^diff-tree ' | cut -b 11- |
>> git diff-tree --stdin -p -v
>>
>> Is this the real way to do it? Do others do something similar?
>
> Depends on how did you created your git-svn repo. If you have only one
> branch with no prefix, then I would try:
>
> git log git-svn..master
>
prev parent reply other threads:[~2008-07-29 0:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 22:54 Showing changes about to be commited via git svn dcommit Lee Marlow
2008-07-28 23:53 ` Miklos Vajna
2008-07-29 0:32 ` Lee Marlow [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=7968d7490807281732x27a3987cka664ae64351f6751@mail.gmail.com \
--to=lee.marlow@gmail.com \
--cc=git@vger.kernel.org \
--cc=vmiklos@frugalware.org \
/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).