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

2010-04-16 Thread Raphael Hertzog
Hi, sorry for the delay answering. On Mon, 29 Mar 2010, Colin Watson wrote: I don't know that we need to bother with two fields, though. There's precedent in DEP-3 for fields with internal structure; the format of Origin is not dissimilar to what we need here. How about something like the

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

2010-04-16 Thread Benjamin Drung
Am Freitag, den 16.04.2010, 22:48 +0200 schrieb Raphael Hertzog: Hi, sorry for the delay answering. On Mon, 29 Mar 2010, Colin Watson wrote: I don't know that we need to bother with two fields, though. There's precedent in DEP-3 for fields with internal structure; the format of

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

2010-03-29 Thread Colin Watson
On Mon, Nov 23, 2009 at 04:26:21PM +0100, Goswin von Brederlow wrote: Benjamin Drung bdr...@ubuntu.com writes: Am Montag, den 23.11.2009, 09:18 +0100 schrieb Goswin von Brederlow: Benjamin Drung bdr...@ubuntu.com writes: When a new upstream version is released, I have to check all patches

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

2009-11-23 Thread Benjamin Drung
Am Montag, den 23.11.2009, 08:42 +0100 schrieb Raphael Hertzog: Hi, On Mon, 23 Nov 2009, Benjamin Drung wrote: 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

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

2009-11-23 Thread Goswin von Brederlow
Benjamin Drung bdr...@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

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

2009-11-23 Thread Benjamin Drung
Am Montag, den 23.11.2009, 09:18 +0100 schrieb Goswin von Brederlow: Benjamin Drung bdr...@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

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

2009-11-23 Thread Mike Hommey
On Mon, Nov 23, 2009 at 09:18:37AM +0100, Goswin von Brederlow wrote: Benjamin Drung bdr...@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

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

2009-11-23 Thread Goswin von Brederlow
Benjamin Drung bdr...@ubuntu.com writes: Am Montag, den 23.11.2009, 09:18 +0100 schrieb Goswin von Brederlow: Benjamin Drung bdr...@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

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

2009-11-22 Thread Benjamin Drung
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

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

2009-11-22 Thread Raphael Hertzog
Hi, On Mon, 23 Nov 2009, Benjamin Drung wrote: 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