m...@linux.it (Marco d'Itri) writes:
> On May 18, Russ Allbery <r...@debian.org> wrote:
>> I do this work in cases where keeping the patches separate is useful for
>> some reason, but mostly it's not.
> Some of my packages have 30-60 patches ("mature" software...), and
> merging them would make them impossibile to understand.
> Is there a VCS workflow which would make such packages easier to manage
> than with quilt? (I like quilt, BTW.)
In cases like that where quilt is already doing what I want, I've been
known to just check the patches into Git and make sure that I only do git
commits after quilt pop -a. I do that with our local builds of Heimdal,
for example.
There are more complicated things that let you serialize your patches from
Git commits and turn them into quilt patch sets, but they're mostly ways
to do something quilt-like in Git while avoiding using quilt directly. If
you're comfortable using quilt directly, I'm not sure they'll buy you
anything.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87wr46yqdy....@windlord.stanford.edu
