On Sun, 2010-11-28 at 22:06 -0600, Jonathan Nieder wrote:
> Paul Wise wrote:
> > On Sun, 2010-11-28 at 12:03 -0600, Jonathan Nieder wrote:
>
> >> Thoughts on this would be very helpful because the same questions come
> >> up in implementing "native" svn support for git.
> >
> > At the very least g
Paul Wise wrote:
> On Sun, 2010-11-28 at 12:03 -0600, Jonathan Nieder wrote:
>> Thoughts on this would be very helpful because the same questions come
>> up in implementing "native" svn support for git.
>
> At the very least git svn --convert should do these:
>
> 1. SVN tags that are actuall
On Sun, 2010-11-28 at 12:03 -0600, Jonathan Nieder wrote:
> Thoughts on this would be very helpful because the same questions come
> up in implementing "native" svn support for git.
At the very least git svn --convert should do these:
1. SVN tags that are actually tags in SVN (ie dir copies
Hi,
Sorry for the long silence.
sean finney wrote:
> tagging the known working cases and leaving the rest of them as branches
> would work, but would leave you with a slightly inconsistant result (i.e.
> you'd also probably want to warn the user that they're missing some tags).
>
> here's a few
severity 501761 wishlist
quit
On Fri, Oct 10, 2008 at 09:19:43AM +0200, Gerfried Fuchs wrote:
> git-svn -s (or --tags=) assumes that all tags subdirectories can be
> changed and doesn't even try to use tags but creates branches right
> ahead. When wanting to convert from svn to git this is really
Package: git-svn
Version: 1:1.5.6.5-1
Severity: normal
Hi!
git-svn -s (or --tags=) assumes that all tags subdirectories can be
changed and doesn't even try to use tags but creates branches right
ahead. When wanting to convert from svn to git this is really a pain,
and I don't see why it
6 matches
Mail list logo
