Skip to content

Replying to bug reports

3 messages · Roger D. Peng, Martin Maechler, Uwe Ligges

#
I have a naive question here, but only because I've managed to screw 
this up twice in the last week.

What is the correct way to reply to a bug report?

Should r-bugs be in the To: or Cc: fields?  I originally thought that 
hitting "Reply" and stripping of the r-devel email address was 
sufficient but apparently not.

-roger
#
Roger> I have a naive question here, but only because I've
    Roger> managed to screw this up twice in the last week.

    Roger> What is the correct way to reply to a bug report?

    Roger> Should r-bugs be in the To: or Cc: fields?  I
    Roger> originally thought that hitting "Reply" and stripping
    Roger> of the r-devel email address was sufficient but
    Roger> apparently not.

and be careful to keep the string '(PR#....)' as part of the
subject *)  That should really suffice.

Can you remind me of an example where it didn't?

Martin

*)
 Brian found it useful to move that string to the
 beginning of the subject line in those cases where that line
 has been relatively long -- since other people's mailers may
 break the line in two - which for the 'R-bugs' mail handler
 makes the 2nd part to be "not Subject" and leads to creation of
 another PR#.
#
Martin Maechler wrote:

            
Indeed, see yesterdays the duplicated reports #7100 and #7102. Where it 
would have been essential (at least for Roger's mail client) to move the 
PR#7100 in front of the subject line.

I don't know JitterBug. Is it possible to put the PR# in front of the 
subject line rather than appending it at the end in order to overcome 
this quite frequent problem with rather long subject lines?

Uwe