From: Mike Frysinger <vapier@gentoo.org>
To: Chen Gang S <gang.chen@sunrus.com.cn>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] sim/ChangeLog: Correct the related items' position and format.
Date: Thu, 19 Feb 2015 02:22:00 -0000 [thread overview]
Message-ID: <20150219022223.GD544@vapier> (raw)
In-Reply-To: <54E53730.4060102@sunrus.com.cn>
[-- Attachment #1: Type: text/plain, Size: 270 bytes --]
On 19 Feb 2015 09:06, Chen Gang S wrote:
> --- a/sim/ChangeLog
> +++ b/sim/ChangeLog
>
> + * ChangeLog: Move sub-modules related items to their own
> + ChangeLogs.
heh, so meta. i'm not sure we generally do this ... does anyone else have input
here ?
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-19 2:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 0:59 Chen Gang S
2015-02-19 2:22 ` Mike Frysinger [this message]
2015-02-19 11:01 ` Pedro Alves
2015-02-19 11:40 ` Chen Gang S
2015-02-19 11:48 ` Pedro Alves
2015-02-19 12:12 ` Chen Gang S
2015-02-19 15:56 ` Michael Eager
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=20150219022223.GD544@vapier \
--to=vapier@gentoo.org \
--cc=gang.chen@sunrus.com.cn \
--cc=gdb-patches@sourceware.org \
/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