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

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

 



On 2008-05-07 22:25:04 -0400, Chris Shoemaker wrote:

> On Wed, May 07, 2008 at 07:08:50PM -0700, Steven Grimm wrote:
>
> > 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.

Also, one mustn't use Subversion's ability to retroactively edit
commit messages. (Guess what we tend to do from time to time where I
work.)

What'd really be needed to get all of the corner cases right, I think,
is a single import point that everyone else pulls from. The patch that
started this thread would help that scenario, since it makes it
possible to pull from such a central import point, and then run the
dcommit locally. (There's still the problem that dcommit will do a
local import if necessary -- that would have to be fixed as well.
Maybe simply teach git-svn to always try to pull from a given git
repository before hitting the real svn repo.)

-- 
Karl Hasselström, kha@xxxxxxxxxxx
      www.treskal.com/kalle
--
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]

  Powered by Linux