Re: Accepted kaffe 1:1.1.1-1 (i386 source)
Junichi Uekawa <dancer@netfort.gr.jp> wrote:
> > > * New upstream release \1
> > > * fixed "BTS summary line of #1" Closes: #1
> > > * fixed "BTS summary line of #2" Closes: #2
> > > * fixed "BTS summary line of #3" Closes: #3
> > >
> > > in changelogs would probably go a lot further to correcting this
> > > very minor issue than reopening dozens of bug reports that belong
> > > closed, annoying users with BTS garbage, and repeating the same
> > > thread on debian-devel over and over.
> >
> > Yes, that sounds pretty intesresting; an addition to debian-changelog-mode
> > would be interesting.
> >
> > It should be possible to get bugs.debian.org/xxxx and parse the resulting
> > HTML for the title and the original submitter, and placing it.
> >
> > Some addition to debian-changelog-close-bug, possibly optional,
> > that utilizes debian-bug-* (there's no debian-bug-to-buffer... hmm?)
> > to parse the bugreport ?
>
>
> Here is what the output looks like:
>
> ecasound2.2 (2.3.0-1) UNRELEASED; urgency=low
>
> * New upstream release
> * Run autoconf-automae-libtool in build.
> * jackd requires /proc/cpuinfo information not available on zaurus
> From: Junichi Uekawa (closes: #207435)
>
> -- Junichi Uekawa <dancer@debian.org> Sat, 30 Aug 2003 13:16:07 +0900
>
> and here is the patch against debian-bug.el and debian-changelog-mode.el
Thanks for CC'ing me. I catch up on -devel only sporadically.
I'm not sure what the goal is?
Why do you want the bug submitter named in the Closes entry?
If its the title you want, then that is already available after the bug
list has been fetched. I've been wanting to use the title as initial
input to the close command for a wgile, but wasn't convinced it was good
enough. I guess it's a good first stab. That's what you guys want?
Peter
Reply to: