From: "Troy Telford" <ttelford.groups@gmail.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git-svn bug?
Date: Wed, 15 Nov 2006 16:09:31 -0700 [thread overview]
Message-ID: <op.ti2yl5i8zidtg1@rygel.lnxi.com> (raw)
In-Reply-To: <m2psbocpbo.fsf@ziti.local>
> I always send commits as:
>
> git-svn dcommit remotes/git-svn..master
>
> Possibly replacing master with whatever git branch I'm working on.
I get essentially the same error:
fatal: Not a valid object name 92e2e0c50bbbacb0a3426b2c0f8b3e043eb4830a~1
> One nice thing about this approach is that you can sort of preview the
> commit as:
>
> git diff remotes/git-svn..master
>
> [but that just shows overall diffs and git-svn dcommit will apply each
> commit in master separately to svn]
Since I actually checked out a branch, I assume that
git diff remotes/git-svn..svn
should be empty, right?
And if that's the case `git diff svn..master` should be identical to `git
diff remotes/git-svn..svn`?
If I write the diff to a file, it is about 294k in size. Also worth
mentioning is that I'm also tracking binary files in the git repository as
well. It's for an RPM tree, so I have the (binary) package source
tarballs (in a few cases >100 MB tarball) and their corresponding (text)
patches and .spec files.
--
prev parent reply other threads:[~2006-11-15 23:13 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
2006-11-16 15:32 ` Seth Falcon
2006-11-15 23:09 ` Troy Telford [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=op.ti2yl5i8zidtg1@rygel.lnxi.com \
--to=ttelford.groups@gmail.com \
--cc=git@vger.kernel.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).