Re: git-svn bug?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.
--
Troy Telford
-
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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]