[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Applied-Upstream field for Patch Tagging Guidelines (DEP-3)

Am Montag, den 23.11.2009, 09:18 +0100 schrieb Goswin von Brederlow:
> Benjamin Drung <bdrung@ubuntu.com> writes:
> > Hi,
> >
> > When a new upstream version is released, I have to check all patches if
> > they were accepted by upstream or not. I have to check each patch if I
> > can drop it. It would make packaging new releases easier if there were
> > an optional Applied-Upstream field. Every patch that was applied
> > upstream can be dropped. "no" or "not-yet" would indicate that the patch
> > was not applied yet. If the patch was applied, it could contain the
> > revision (like "r4681") or a link to the VCS commit.
> >
> > What do you think about my suggestion?
> Why would the source (or VCS head) ever contain a patch that was
> applied upstream? The moment the patch gets applied you simply remove
> it.

Not until the next upstream release.

Benjamin Drung
Ubuntu Developer (www.ubuntu.com) | Debian Maintainer (www.debian.org)

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil

Reply to: