Re: Tracking divergence from upstream as a bug

2008-05-17 Thread Russ Allbery
Ben Finney <[EMAIL PROTECTED]> writes: > Joey Hess <[EMAIL PROTECTED]> writes: >> (And then an automatic system closing any I forget to mention would be >> nice.) > What information would trigger such automation, in the absence of you > noting it as such in the changelog entry? For a patch that

Re: Tracking divergence from upstream as a bug

2008-05-18 Thread Neil Williams
On Sat, 2008-05-17 at 23:01 -0400, Joey Hess wrote: > Ben Finney wrote: > > Care to discuss what tags you plan to use, so an attempt at consensus > > can be made on naming the tags for this purpose? > > I'm using a "divergence" usertag, with users [EMAIL PROTECTED] and > [EMAIL PROTECTED] (so it'l

Re: Tracking divergence from upstream as a bug

2008-05-18 Thread Ben Finney
Neil Williams <[EMAIL PROTECTED]> writes: > However, from a bug submitter point of view, I don't think I want to > see the bug report kept open (tagged divergence) after it has > actually been closed by a Debian-specific patch. As upstream it > might make a fair bit of sense but as a user / bug su

Re: Tracking divergence from upstream as a bug

2008-05-18 Thread Neil Williams
On Sun, 2008-05-18 at 18:43 +1000, Ben Finney wrote: > Neil Williams <[EMAIL PROTECTED]> writes: > > > However, from a bug submitter point of view, I don't think I want to > > see the bug report kept open (tagged divergence) after it has > > actually been closed by a Debian-specific patch. As upst

Re: Tracking divergence from upstream as a bug

2008-05-18 Thread Don Armstrong
On Sun, 18 May 2008, Neil Williams wrote: > Yes - supported by the use of (Fixed: #1234) in > debian/changelog, .changes etc. and a revised interface for PTS and DDPO > to discriminate between Fixed and Closed bugs. I could easily handle this by just not archiving bugs tagged divergence; when it's

Re: Tracking divergence from upstream as a bug

2008-05-18 Thread Neil Williams
On Sun, 2008-05-18 at 18:51 +0100, Don Armstrong wrote: > On Sun, 18 May 2008, Neil Williams wrote: > > Yes - supported by the use of (Fixed: #1234) in > > debian/changelog, .changes etc. and a revised interface for PTS and DDPO > > to discriminate between Fixed and Closed bugs. > > I could easily

Tracking divergence from upstream as a bug (was: divergence from upstream as a bug)

2008-05-17 Thread Ben Finney
unted after a while. Perhaps the tone would have been better set by describing this idea as "Tracking divergence from upstream as a bug" in the Subject field. -- \"When you go in for a job interview, I think a good thing to

Tracking divergence from upstream as a bug (was: divergence from upstream as a bug)

2008-05-17 Thread Ben Finney
Joey Hess <[EMAIL PROTECTED]> writes: > Hmm, another thought is, I sometimes have a changelog like this: > > * New upstream release. > - Including my fix for foo. > - And a better approach than my old hack to fix bar. > > It would be nice to be able to add bug numbers to close the > divergen

Tracking divergence from upstream as a bug (was: divergence from upstream as a bug)

2008-05-17 Thread Ben Finney
Joey Hess <[EMAIL PROTECTED]> writes: > I think that going back and collecting all the patches I've sent to > upstreams over the years, and any I've dropped on the floor, and > keeping it up-to-date going forward will help me maintain my > packages better anyway, so I plan to do that this week. Th

Re: Tracking divergence from upstream as a bug (was: divergence from upstream as a bug)

2008-05-17 Thread Joey Hess
Ben Finney wrote: > Care to discuss what tags you plan to use, so an attempt at consensus > can be made on naming the tags for this purpose? I'm using a "divergence" usertag, with users [EMAIL PROTECTED] and [EMAIL PROTECTED] (so it'll show up on my bugs page, and the package's bug page -- not ide