Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Gdb List <gdb@sources.redhat.com>
Subject: Re: Mentioning PR's in ChangeLogs
Date: Fri, 23 Feb 2001 23:39:00 -0000	[thread overview]
Message-ID: <87u25k1pv2.fsf@creche.redhat.com> (raw)
In-Reply-To: <3A8D7872.18F39077@cygnus.com>

>>>>> "Andrew" == Andrew Cagney <ac131313@cygnus.com> writes:

Andrew> So anyone know what correct protocol is?  A ChangeLog should
Andrew> definitly standup on its own right vis:
Andrew> 	* foo.c: Fix pr/12
Andrew> being definitly invalid.  Beyond that, I don't know.

FYI: on sources, if your CVSROOT/loginfo is set up properly, you can
have commits which mention a PR automatically be appended to the PR.

You have to mention the PR in the commit message with the correct
syntax, namely it must contain the text `PR category/NNN', where
`category' is the correct category name for the PR and `NNN' is the PR
number.

This puts the commit message into the PR.  If you've turned on cvsweb
URLs for the commit messages (again in loginfo) then this provides a
simple gnats/cvs integration: you can go directly from the PR to the
patches which supposedly fixed it.

In gcj-land we've adopted the policy of including text like `Fixed PR
gcj/2929' in the ChangeLog entry.  That's in addition to, not in place
of, whatever other ChangeLog description we write.

Tom


  parent reply	other threads:[~2001-02-23 23:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-16 11:03 Andrew Cagney
2001-02-16 11:18 ` J.T. Conklin
     [not found] ` <200102162004.PAA23865@indy.delorie.com>
2001-02-23 14:02   ` Andrew Cagney
2001-02-24  0:09     ` Eli Zaretskii
2001-02-26  8:36       ` Andrew Cagney
2001-02-23 23:39 ` Tom Tromey [this message]
2001-02-26  8:40   ` 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=87u25k1pv2.fsf@creche.redhat.com \
    --to=tromey@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb@sources.redhat.com \
    /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