On Wed, Nov 07, 2012 at 09:26:28AM +0100, Raphael Hertzog wrote: > (Dropping the bug) > > On Tue, 06 Nov 2012, Steve Langasek wrote: > > Private mails should not be a justification for expedited orphaning of > > packages. With this bug report you have *now* used a proper channel for > > notifying the maintainer that you want to salvage the package; so the clock > > starts now, not whenever your private mail was sent. > > I disagree. Private mails (barring mistakes) are more likely to be > effective ways to reach a maintainer that looks busy. My BTS mails > is stored in folders that I will not open when I'm really swamped but > I do always read my private mails. I disagree with you too. Private _only_ mails are not the way to handle a public issue. There's no reason not to Cc the bug you're concerned about or opening a new one and then Cc it in your direct email to the maintainer. > We can institude to CC debian-email@lists.debian.org on similar private > mails so that they are archived (non-publicly) for other DD to investigate > in case it's needed (see master:/srv/mail-archives/archive/debian-email). > > But private mails should count in the ITO evaluation. Nope, if there's no public record there's no guarantee it was delivered. Did you forget mail is not a realiable service? -- Ricardo Mones ~ Don't take the name of root in vain. /usr/src/linux/README
Attachment:
signature.asc
Description: Digital signature