Re: Tools

[Krzysztof Krzyżaniak <eloy@kofeina.net>]

Russ Allbery wrote:
> Joey Hess <joeyh@debian.org> writes:
> 
>> I think/hope I explained the why in the blog post.
>>
>> I like to use the awesome power of a modern version control system, be
>> it svn or git, to manage my patches. They're both pretty good, and tools
>> like svn-upgrade make it easy to merge my changes forward to a new
>> upstream release. svn is less good than git at handling things like
>> feature or bugfix branches. If I have a lot of branches, I'm happier
>> working with git these days. I've never found myself in that position
>> with a CPAN package though. CPAN packages tend to need very few
>> modifications.
> 
> Just adding a perspective, not trying to convince you particularly:
> 
> I still find it really important to be able to separate out individual
> changes to feed upstream when working with a CPAN package.  With quilt, I
> can do that.  With git, I can do that, but the team isn't using git and
> doesn't have a git respository (and has a bunch of tools that need to know
> about the repository).  With Subversion, I can't do that, so just making
> the modifications directly in Subversion looks really unappealing.  It
> adds to the upstream coordination work and makes it harder to cope with
> new versions for me.

svk, you can use it parallel with subversion upstream repo.

  eloy
-- 
-------e-l-o-y----------------------------e-l-o-y-@-k-o-f-e-i-n-a-.-n-e-t------

       jak to dobrze, ¿e s± oceany - bez nich by³oby jeszcze smutniej