public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christian Faulhammer <fauli@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Use full package atoms for bug reports
Date: Tue, 6 Jan 2009 00:49:54 +0100	[thread overview]
Message-ID: <20090106004954.42051799@terra.solaris> (raw)
In-Reply-To: <20090104174353.22981e4e@epia.jer-c2.orkz.net>

[-- Attachment #1: Type: text/plain, Size: 849 bytes --]

Hi,

Jeroen Roovers <jer@gentoo.org>:
> On Sun, 4 Jan 2009 14:52:11 +0100
> Christian Faulhammer <fauli@gentoo.org> wrote:
> > Please be so kind and use full package atoms in the bug description
> > line (especially when bug wrangling), searching is made easier that
> > way.
> 
>   "Bug reports that refer to a single or a few (similar) packages
>   should detail the package atom(s) as completely as possible in the
>   Summary, including a version only when other versions do not exhibit
>   the bug."[1]

 I know that piece, I wrote the initial version of that paragraph. :)
But some people who are allowed to assign directly (mostly developers)
tend to forget it.

V-Li

-- 
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode

<URL:http://www.faulhammer.org/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      parent reply	other threads:[~2009-01-05 23:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-04 13:52 [gentoo-dev] Use full package atoms for bug reports Christian Faulhammer
2009-01-04 16:43 ` Jeroen Roovers
2009-01-04 23:45   ` [gentoo-dev] " Duncan
2009-01-04 23:52     ` Mike Auty
2009-01-05  6:58       ` Duncan
2009-01-05 23:49   ` Christian Faulhammer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090106004954.42051799@terra.solaris \
    --to=fauli@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox