On Thu, 25 Sep 2014, Neil Williams wrote:
> Use the bug title as the subject when replying to a message using the
> reply link and when replying to the bug report directly from the bug
> number link at the top of the page.
>
> That avoids problems with the package being a pseudo-package were the
>
On Thu, 25 Sep 2014 10:30:09 -0700
Don Armstrong wrote:
> On Wed, 24 Sep 2014, Neil Williams wrote:
> > Please always include the package name / topic in the subject of the
> > email or, as a matter of last resort, in the first few lines of the
> > content of the message.
>
> This requires a lot
On Wed, 24 Sep 2014, Neil Williams wrote:
> Please always include the package name / topic in the subject of the
> email or, as a matter of last resort, in the first few lines of the
> content of the message.
This requires a lot of work on the part of the sender.
Currently, the package is already
On Wed, 24 Sep 2014, Jakub Wilk wrote:
> > You can easily do this by downloading an email from the bug thread and
> > replying to that.
>
> Luckily, if you do that, there's a great chance that you'll get both a helpful
> Subject and References. :-)
Except if it’s the first mail in the thread, th
On Wed, 24 Sep 2014 18:30:28 +0100
Neil Williams wrote:
One other idea - maybe the top level reply link (the one showing the bug
number at the very top of the page) could use the current bug title as
the subject of the reply rather than leaving it blank?
--
Neil Williams
=
http://
On Wed, 24 Sep 2014 19:10:54 +0200
Jakub Wilk wrote:
> * David Prévot , 2014-09-24, 06:32:
> >Or convince the BTS maintainers that #744339 is actually worth
> >fixing (the subjects already get mangled to add the bug number one
> >can already see in the To: field anyway, adding the package name on
* David Prévot , 2014-09-24, 06:32:
Or convince the BTS maintainers that #744339 is actually worth fixing
(the subjects already get mangled to add the bug number one can already
see in the To: field anyway, adding the package name on top or instead
of it wouldn’t be such a bad move IMHO).
So
* Emilio Pozuelo Monfort , 2014-09-24, 12:10:
On 24/09/14 11:46, Neil Williams wrote:
can people from this list *please* include something specific to the
actual package/topic in the Subject of emails to bug reports? At the
very least, something in the first few lines of the content saying
wha
On Wed, Sep 24, 2014 at 12:32 PM, David Prévot wrote:
> Or convince the BTS maintainers that #744339 is actually worth fixing
> (the subjects already get mangled to add the bug number one can already
> see in the To: field anyway, adding the package name on top or instead
> of it wouldn’t be such
Hi,
[Full quote of the intitial message for the benefit of the BTS archive.]
> On 24/09/14 11:46, Neil Williams wrote:
>> This is a particularly common problem with team maintenance packages or
>> with psuedo-packages (like release.debian.org) where a lot of people
>> may be on the list.
>>
>> Pl
Hi,
>> Or even better: properly set In-Reply-To / References. You can easily
>> do this by downloading an email from the bug thread and replying to
>> that.
>
> Good advice. It's as easy as:
>
> $ bts show --mbox
>
> or add the ‘--mailreader=foo’ option if you want a MUA other than Mutt.
Emilio Pozuelo Monfort writes:
> Or even better: properly set In-Reply-To / References. You can easily
> do this by downloading an email from the bug thread and replying to
> that.
Good advice. It's as easy as:
$ bts show --mbox
or add the ‘--mailreader=foo’ option if you want a MUA other
On 24/09/14 11:46, Neil Williams wrote:
> This is a particularly common problem with team maintenance packages or
> with psuedo-packages (like release.debian.org) where a lot of people
> may be on the list.
>
> Please always include the package name / topic in the subject of the
> email or, as a m
13 matches
Mail list logo
