>>>>> "adeodato" == Adeodato Simó <[EMAIL PROTECTED]> writes:
adeodato> * Bernhard Fischer [Fri, 20 May 2005 18:23:14 +0200]: >> Hi, adeodato> Hi Bernhard, I'm not a dpkg person at all, but the adeodato> following advice sounds like common sense to me, and adeodato> perhaps it even helps. ;-) Hello to both :-D >> Attached patch implements support for transparent terminals in >> dselect. It also contains various cosmetic fixes as well as a >> potential real bug in lib/varbuf.c. adeodato> What about spliting the thing into three separate adeodato> patches then? They are certainly three separate issues, adeodato> with three different priorities, so chances are that adeodato> some will get applied before than the others. Yes. This is really better. Is best if you have fixes and improvements in two or more patches. >> PS: The patch is against dpkg-1.10.27 from testing as gluck was >> down at the time i wrote it. adeodato> As I can't be sure the above implies you're aware of adeodato> it, I'll mention: development on dpkg is happening on adeodato> the experimental version (1.13.4 atm), so it'd be adeodato> helpful to make sure your patch is up to date. There's adeodato> also an Arch repo, so if you're familiar with it you may adeodato> want to maintain a branch. I suggest instead of plain patches try to use arch or bazaar and make one branch for each feature. Then you can sync your patches easier and is a lot easier for dpkg hackers merge them too. Of course, use the development branch for include new features since it will probably be moved to unstable when sarge goes out. -- O T A V I O S A L V A D O R --------------------------------------------- E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio --------------------------------------------- "Microsoft gives you Windows ... Linux gives you the whole house."