On Wed, Sep 13, 2000 at 12:38:58AM -0700, Joey Hess wrote: > Ben Collins wrote: > > > I think aside of one diff or many diffs a list of patches done to the code > > > and where you got them from is a good thing to have in every package. > > > > Most patches are done by the maintainer, or submitted as bug reports. Those > > are listed in the changelog, but even then, it doesn't help dereference the > > patched source to it's individual patches. > > This is a really easy thing to do. It's called commenting your patches. > > And woe upon the developer who does not.
Still requires manual editing of the .diff.gz to remove them on a per/patch basis (if for example your 10k/5 file patch gets merged upstream, but the rest of your 50k of patches don't). Also, if someone else wants just that patch (backport to a different version) they have to manually go through the .diff.gz aswell. My solution still wins :) -- -----------=======-=-======-=========-----------=====------------=-=------ / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=========------=======-------------=-=-----=-===-======-------=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]