boilerplate messages in bugs

[Leann Ogasawara]

On Fri, 2008-09-12 at 13:58 +0930, Karl Goetz wrote:
> On Thu, 2008-09-11 at 10:38 -0700, Leann Ogasawara wrote:
> > On Thu, 2008-09-11 at 15:26 +0930, Karl Goetz wrote:
> > > On Wed, 2008-09-10 at 09:32 -0700, Leann Ogasawara wrote:
> > > > On Wed, 2008-09-10 at 17:41 +0930, Karl Goetz wrote:
> > > I guess it depends on the level of automation.
> > > If theres a human doing the pasting, i dont think its unreasonable to
> > > think that a bug title that refers to /path/to/foo.c would be left out
> > > of a call to test a binary kernel.
> > > If its completely automatic, then that makes it somewhat harder.
> > > I dont know how LP works for a 'hands off' level of automation (indeed,
> > > i dont know if it can at all), so i cant comment on wether it can be
> > > told to ignore some bugs in mails like that.
> > 
> > Using python-launchpad-bugs we could ignore posting to bug reports which
> > had a specific tag.
> 
> Are their tags for source/binary problem?

I don't believe tags exist for this at the moment.

> Perhaps something to indicate a bug is source related (eg, copyright
> issue) as oposed to binary (eg, crasher).

Sure.  We'd just need to come to an agreement for the tag name and then
tag bug reports accordingly.  I'll also raise this at the next QA
meeting to get more feedback.

Thanks,
Leann