-=| gregor herrmann, Sun, Dec 19, 2010 at 07:34:52PM +0100 |=-
> On Sun, 19 Dec 2010 14:55:38 +0200, Peter Pentchev wrote:
>
> > You do mention that in the interest of preserving history, git-import-dsc
> > may be used more than once with all the .dsc files available, and that's
> > indeed one of its great features. What I wonder is, is there a way to
> > use git-svn and "git svn clone" in particular to preserve *all* of
> > a package's Subversion history, while still keeping the git-import-dsc
> > style of branching and stuff?
>
> Usual disclaimer: /me = git n00b
>
> There seem to be some tutorials around for this purpose, one I found
> today is http://wiki.debian.org/Games/VCS/git/converting-from-svn
> (usual disclaimer ...)
That should work more or less (there is a ready AUTHORS file somewhere
in /git/pkg-perl), but I don't like the general direction of this. We
aren't yet converting pkg-perl from Svn to Git. Doing so now will
break the workflow as PET can't see the Git repositories.
The purpose of the Git guide is to give some pointers to people who
are ready to sacrifice the PET integration in favour of using the tool
they love.
("I'll use Git or else I'll maintain it outside the group!")
("I can upload/take care of it myself, PET doesn't give me that much,
and Git is so c00l")
All this said, having a developed procedure for the conversion ready
at hand cannot be bad. And if we live to see the day of PET supporting
Git, we could even use that procedure. And who am I to tell others how
to spend their time anyway? :)
Attachment:
signature.asc
Description: Digital signature