Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: ac131313@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: [patch] gdb.c++/local.exp: add pr numbers
Date: Sat, 13 Apr 2002 17:45:00 -0000	[thread overview]
Message-ID: <1018745148.4364.18.camel@dberlin.org> (raw)
In-Reply-To: <200204132206.g3DM6NE30493@duracef.shout.net>

On Sat, 2002-04-13 at 18:06, Michael Elizabeth Chastain wrote:
> Andrew Cagney writes:
> > Suggest just ``(gdb/482)''.  It appears GCC really is switching to 
> > Bugzilla so ``gnats'' may one day not apply.
> 
> I thought about that.  When we switch to Bugzilla, is the bug still
> going to be #482? 
Yes.
Bugzilla bug ids for gnats bugs will be the same as they were for gnats.

> I like "gnats:gdb/482" because it identifies the bug
> reporting system that actually contains the bug.


> 
> I don't know if there's a standard way of citing bug reports ...
> do you want to promulgate one?

Um, if you simply write something fitting the regex bug(\s|%\#)*(\d+) ,
bugzilla will make it link to the bug in question.

If you want to reference a comment in the same bug, simply writing
something fitting comment(\s|%\#)*(\d+) will link to that comment

And combining the two, with an optional comma 
     bug(\s|%\#)*(\d+),?\s*comment\s*(\s|%\#)(\d+)     
will link to to a specific comment in a specific bug.

This is the basic standard for citing bug reports (Also FYI: There is no
official standard way for citing them in "real" documents, other than
using the proper citation form for their URL's or something.)

I'm not going to modify the bugzilla source (to recognize any other
citation forms, as this highlighting is done in a routine used all over
the place (and thus, it's harder to verify a given regex does what you
expect in all cases), and I am specifically trying to avoid making any
changes to the perl source that can be avoided (the templates are
expected to be changed).

> 
> Michael C


  reply	other threads:[~2002-04-14  0:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-13 15:06 Michael Elizabeth Chastain
2002-04-13 17:45 ` Daniel Berlin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-22 22:19 Michael Elizabeth Chastain
2002-04-22 22:17 Michael Elizabeth Chastain
2002-04-21 20:29 Michael Elizabeth Chastain
2002-04-14  1:02 Michael Elizabeth Chastain
2002-04-13 23:41 Michael Elizabeth Chastain
2002-04-14  0:12 ` Daniel Berlin
2002-04-14  6:31   ` Andrew Cagney
2002-04-14  8:22   ` Tom Tromey
2002-04-20 18:45 ` Andrew Cagney
2002-04-12 18:24 Michael Elizabeth Chastain
2002-04-12 15:27 Michael Elizabeth Chastain
2002-04-12 17:08 ` Kevin Buettner
2002-04-12 17:20   ` Daniel Jacobowitz
2002-04-13 14:58 ` Andrew Cagney

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=1018745148.4364.18.camel@dberlin.org \
    --to=dberlin@dberlin.org \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec@shout.net \
    /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