Re: [PATCH] Teach git-svn how to catch up with its tracking branches

[Chris Shoemaker <c.shoemaker@cox.net>]

On Wed, May 07, 2008 at 07:08:50PM -0700, Steven Grimm wrote:
> On May 7, 2008, at 6:58 PM, Chris Shoemaker wrote:
>> Second, what will happen when different developers have svn URLs with
>> different schemes, e.g. http vs. svn+ssh?
>
> That will cause the commit messages to be different, which means you won't 
> have the same commit hashes, so this pretty much won't be useful. (You'd 
> end up fetching the remote repo's entire svn history if you tried to do git 
> fetch.)

Yes, indeed.  But git fetching even the entire svn history is probably
often faster than git-svn fetching even one commit!  I guess the
question is really, if I replace my remote tracking branch with
someone else's remote tracking branch, and it invalidates old map
entries, what breaks?  Note, that even a slight difference in
svn.authorsfile would have the same effect.

> The assumption here is that you have exactly the same revision history in 
> your tracking branches as the repo you're fetching from.

In that case, it would be helpful to enumerate exactly how two
developers can ensure that they are creating the same revision
history.  At the very least, svn URL scheme and svnauthors file have
to be the same.

-chris