From: Eli Zaretskii <eliz@is.elta.co.il>
To: cgd@broadcom.com
Cc: ac131313@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFA] two MIPS opcodes patches to pull up to branch?
Date: Mon, 25 Mar 2002 03:06:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1020325130245.14639A-100000@is> (raw)
In-Reply-To: <yov5n0wx17g4.fsf@broadcom.com>
On 24 Mar 2002 cgd@broadcom.com wrote:
> 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.
For changes on the branch, you are supposed to modify the ChangeLog
files from the branch only. The date should be the date of the commit
(otherwise, the logs are not in chronological order, which makes it hard
to track change history).
In other words, you should do the same as you do on the trunk. That's
why there's no mention of anything special in the branch policy text.
next prev parent reply other threads:[~2002-03-25 11:06 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
2002-03-25 3:06 ` Eli Zaretskii [this message]
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=Pine.SUN.3.91.1020325130245.14639A-100000@is \
--to=eliz@is.elta.co.il \
--cc=ac131313@cygnus.com \
--cc=cgd@broadcom.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