Advantages of simpler patch management tools

[Remi Vanicat]

2007/10/12, Kumar Appaiah <akumar at ee.iitm.ac.in>:
> While using a vcs to put the packages might be very convenient,
> doesn't this go against the thumb rule of keeping your .diff.gz `clean'?
> I mean, the rule is, that your .diff.gz should have only the contents
> of the debian/ directory, but this won't ensure that, right? I would
> be interested in knowing your views about this.

I believe that the security team had tell us that they prefer at the
opposite to have a diff.gz where all the patch are applied, so that
they don't have to know which patch system we use to make a security
fix on a package.

So one can prefer not to follow this rule (I do)

[...]

> My question to madduck was, if you use a .git.tar.gz to replace the
> old style .diff.gz approach, won't this actually make things difficult
> for wannabe patch senders who don't know git? Won't they prefer the
> old style .diff.gz instead?

I've the same concern. Can we ask to all contributor to our package to
know how to use git ?