Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: cgd@broadcom.com
To: ac131313@cygnus.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFA] two MIPS opcodes patches to pull up to branch?
Date: Sun, 24 Mar 2002 22:34:00 -0000	[thread overview]
Message-ID: <yov5n0wx17g4.fsf@broadcom.com> (raw)
In-Reply-To: ac131313@cygnus.com's message of "Sun, 17 Mar 2002 01:49:40 +0000 (UTC)"

At Sun, 17 Mar 2002 01:49:40 +0000 (UTC), "Andrew Cagney" wrote:
> Yep, fine.  What's the worst that could happen, the mips breaks? :-)

What's the format to be used for branch ChangeLogs?

change log as originally committed (i.e., using original commit date)?
new entry at top of file or sorted in by original date?  etc.

I didn't see anything about this in your recently posted branch
policy...


thanks,

chris


  parent reply	other threads:[~2002-03-25  6:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-16 12:16 cgd
2002-03-16 17:46 ` Andrew Cagney
     [not found]   ` <mailpost.1016329780.11992@news-sj1-1>
2002-03-24 22:34     ` cgd [this message]
2002-03-25  3:06       ` Eli Zaretskii
2002-03-25  6:15         ` 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=yov5n0wx17g4.fsf@broadcom.com \
    --to=cgd@broadcom.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@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