Magnus, I agree with your arguments. But yet, we are/were in the situation
when we have to have some strategy how to deal with it.
On Tue, Jul 21, 2015 at 11:01 AM, Magnus Therning <mag...@therning.org>
> On Mon, Jul 20, 2015 at 02:45:36PM -0400, Jan Trmal wrote:
> > John, thanks for your response, I will experiment with your suggestions.
> > Let me clarify details of what I was saying-- I'm not sure if I'm able to
> > express my concern clearly.
> > Both of these repositories ("jtrmal", "vimal") were created from the same
> > svn repository, using git svn clone.
> > The master branches on both repos are the same (up to a few last commits,
> > because they were sync'd at different times) content-wise, the git-svn
> > in the logs are the same, only the sha numbers, are different. I don't
> > understand the reason for that, but I assume there is some randomness
> > initiating the git repository. IIRC the shasum of the commit is
> > of the commit+sha of the parent).
> IIRC there `git-svn` doesn't guarantee that the shasums will be
> identical between two `git svn clone` of the same repo. I'm not sure
> if that's true all the time, but it's clear that some arguments will
> have an influence on the tree of changes (wether branches are
> included, etc), which in turn will influence the shasums.
> I gather this is a reason for the man page of git-svn including the
> following text (at the top of the *caveats* section):
> For the sake of simplicity and interoperating with Subversion, it is
> recommended that all git svn users clone, fetch and dcommit directly
> from the SVN server, and avoid all git clone/pull/merge/push
> operations between Git repositories and branches. The recommended
> method of exchanging code between Git branches and users is git
> format-patch and git am, or just 'dcommit’ing to the SVN repository.
> Magnus Therning OpenPGP: 0xAB4DFBA4
> email: mag...@therning.org jabber: mag...@therning.org
> twitter: magthe http://therning.org/magnus
> Good powers of observation are frequently called "cynicism" by those
> that don't have them.
> You received this message because you are subscribed to a topic in the
> Google Groups "Git for human beings" group.
> To unsubscribe from this topic, visit
> To unsubscribe from this group and all its topics, send an email to
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.