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

Re: On Bugs



Btw, I'm on owner@bugs.debian.org, and am also a part-time debbugs hacker.

On Tue, 3 Oct 2000, Anthony Towns wrote:
> It might also be possible to make use of the `keyword' fields the BTS
> supposedly supports, I'm not sure.

Yes, well, I'm glad you mentioned that.

I was perusing the debbugs source tonight, and noticed that it supported a
keyword: field, when submitting a bug.  However, it's parsing of that field
was broken, so I fixed it.

However, in discussions Anthony and I had on irc, I am going to change the way
my above fix was done.  Here is what I am thinking.

When submitting a bug, the following psuedo-header can be added to the email:

keywords: foo, bar, baz

For control@bugs.debian.org, the following commands become available:

keywords 12345 foo, bar		# Sets the keywords field to the supplied 
				# list.
keywords 12345 + blah		# Adds the given keyword(s) to the list.
addkeywords 12345 baz		# ditto
keywords 12345 - foo		# Deletes the given keyword(s) from the list.
delkeywords 12345 blah		# ditto
listkeywords 12345		# In the response email, list all the keywords
				# the bug has.

This is only a preliminary set of commands.  None of these have been
implemented yet.  Also, the list of allowed keywords would have to be
something that all developers agree on.  Ie, 'fixed', 'patch',
'waitingOnSubmitter', 'WONTFIX', others?

Obviously, once submit@ and control@ can handle keywords, then the cgi scripts
can be modified to do searches on them.

----BEGIN GEEK CODE BLOCK----
Version: 3.12
GCS d- s: a-- c+++ UL++++ P+ L++++ !E W+ M o+ K- W--- !O M- !V PS--
PE++ Y+ PGP++ t* 5++ X+ tv b+ D++ G e h*! !r z?
-----END GEEK CODE BLOCK-----
----BEGIN PGP INFO----
Adam Heath <doogie@debian.org>        Finger Print | KeyID
67 01 42 93 CA 37 FB 1E    63 C9 80 1D 08 CF 84 0A | DE656B05 PGP
AD46 C888 F587 F8A3 A6DA  3261 8A2C 7DC2 8BD4 A489 | 8BD4A489 GPG
-----END PGP INFO-----



Reply to: