m...@linux.it (Marco d'Itri) writes:
> On Mar 09, Russ Allbery <r...@debian.org> wrote:
>
>> I think TopGit is the right solution to this.
> Is it plausible to use a branch-per-patch solution for packages
> containing 30-60 patches?
>
> --
> ciao,
> Marco
>From the space and git point of view that is completly
doable. Branches are dirt cheap.
>From a usability point of view I find it unusable. With so many
branches you always forget to merge one or don't commit to the right
one. And changing branches will change files and if you have them open
in for example emacs it will notice the file was changed on disk and
asks you to revert it, which sucks.
But then again, if you only work on the last patch in the stack then
that isn't a problem.
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
