Bug#1020248: marked as done (debian-policy: Clarifying nomenclature for control file names)

2024-02-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Feb 2024 13:19:24 + with message-id and subject line Bug#1020248: fixed in debian-policy 4.6.2.1 has caused the Debian Bug report #1020248, regarding debian-policy: Clarifying nomenclature for control file names to be marked as done. This means that you claim that

Bug#1020248: marked as done (debian-policy: Clarifying nomenclature for control file names)

2023-01-14 Thread Guillem Jover
Hi! On Sat, 2022-12-17 at 17:24:57 -0700, Sean Whitton wrote: > On Sat 17 Dec 2022 at 04:43PM +01, Guillem Jover wrote: > > Sorry, probably my fault! As I tend to use «Fixes:» git pseudo-fields > > for things that fix part of a bug, but are not intended yet to close it, > > for which I use

Bug#1020248: marked as done (debian-policy: Clarifying nomenclature for control file names)

2022-12-17 Thread Sean Whitton
Hello, On Sat 17 Dec 2022 at 04:43PM +01, Guillem Jover wrote: > Control: reopen -1 > > Hi! > > Sorry, probably my fault! As I tend to use «Fixes:» git pseudo-fields > for things that fix part of a bug, but are not intended yet to close it, > for which I use «Closes:». > > And for some reason I

Bug#1020248: marked as done (debian-policy: Clarifying nomenclature for control file names)

2022-12-17 Thread Guillem Jover
On Sat, 2022-12-17 at 08:35:02 -0800, Russ Allbery wrote: > (That said, and this is only personal preference and I don't feel that > strongly about it, I usually err on the side of creating lots of bugs so > that there can be roughly one bug per patch. It can make it a bit harder > to track

Bug#1020248: marked as done (debian-policy: Clarifying nomenclature for control file names)

2022-12-17 Thread Russ Allbery
Guillem Jover writes: > Sorry, probably my fault! As I tend to use «Fixes:» git pseudo-fields > for things that fix part of a bug, but are not intended yet to close it, > for which I use «Closes:». Ack, sorry, this was my fault. I optimistically added a bug closer when I started merging

Bug#1020248: marked as done (debian-policy: Clarifying nomenclature for control file names)

2022-12-17 Thread Guillem Jover
Control: reopen -1 Hi! Sorry, probably my fault! As I tend to use «Fixes:» git pseudo-fields for things that fix part of a bug, but are not intended yet to close it, for which I use «Closes:». And for some reason I think I also got the impression, even though the stanza changes had been

Processed: Re: Bug#1020248: marked as done (debian-policy: Clarifying nomenclature for control file names)

2022-12-17 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1020248 {Done: Sean Whitton } [debian-policy] debian-policy: Clarifying nomenclature for control file names 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them.

Bug#1020248: marked as done (debian-policy: Clarifying nomenclature for control file names)

2022-12-16 Thread Debian Bug Tracking System
Your message dated Sat, 17 Dec 2022 03:04:04 + with message-id and subject line Bug#1020248: fixed in debian-policy 4.6.2.0 has caused the Debian Bug report #1020248, regarding debian-policy: Clarifying nomenclature for control file names to be marked as done. This means that you claim that