Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: dberlin@dberlin.org, gdb-patches@sources.redhat.com
Subject: Re: [patch] gdb.c++/local.exp: add pr numbers
Date: Sat, 20 Apr 2002 18:45:00 -0000	[thread overview]
Message-ID: <3CC2199E.9000704@cygnus.com> (raw)
In-Reply-To: <200204140640.g3E6etF27586@duracef.shout.net>

> Daniel Berlin writes:
> 
> I am going to hold off on my bug-referencing patches to gdb.c++/*.exp
> while we have some discussion.
> 
> 
>> Bugzilla bug ids for gnats bugs will be the same as they were for gnats.
> 
> 
> Okay.
> 
> 
>> Um, if you simply write something fitting the regex bug(\s|%\#)*(\d+) ,
>> bugzilla will make it link to the bug in question.
> 
> 
> That sounds mostly good to me.  (Right now I am really glad that I've
> learned enough Perl to read those Perl regex's).
> 
> However, it looks like the "gdb" part is implicit, such as:
> 
>   bug %#277

Michael,

Can I suggest, for the moment, we stick with ``gdb/NNNN''.  If/when we 
switch to bugzilla these can be updated as needed.

enjoy,
Andrew


  parent reply	other threads:[~2002-04-21  1:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [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 15:06 Michael Elizabeth Chastain
2002-04-13 17:45 ` Daniel Berlin
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=3CC2199E.9000704@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=dberlin@dberlin.org \
    --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