-=| Peter Pentchev, Sun, Dec 19, 2010 at 09:35:19PM +0200 |=- > On Sun, Dec 19, 2010 at 08:54:09PM +0200, Damyan Ivanov wrote: > "I really like the way the group has been maintaining this package, > and > I fully intend to keep benefitting from it, but I need to fork it for > $REALJOB's needs (extend it a bit and put a different distribution name > in the changelog file... don't ask :) -- and the best way to do that > would be to keep it in a VCS of my own, right here at $REALJOB, and Git > seems to be the best tool for the job, so I would really like a way to > have a local Git repo that I can play with *and* to keep tracking > the Debian Perl Group's changes to the package in the future." Ah, oh. git-svn seems like your tool then. Or even a script that produces a custom package out of the Debian one. Or, ... well you don't need telling that there are many ways :)) > > 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? :) > > Yep, all of your points are good and taken in good faith. Still, IMHO > a svn->git migration is in the not-quite-so-far future, at least for > some packages[0], so gregoa's link[1] just might come in useful at some > point. > > > [0] ...and no, I'm not an advocate of change just for the sake of > change, it's just that IMHO there are quite a few people who think that > Git provides, let's say, a bit more flexibility than Subversion :) Agreed. Sorry if my mail suggested that people want to the change for "fashion" reasons :)
Attachment:
signature.asc
Description: Digital signature