From: Mike Frysinger <vapier@gentoo.org>
To: Doug Evans <dje@google.com>
Cc: GDB <gdb@sourceware.org>
Subject: Re: policy on splitting ChangeLogs?
Date: Wed, 21 Mar 2012 02:26:00 -0000 [thread overview]
Message-ID: <201203202226.46068.vapier@gentoo.org> (raw)
In-Reply-To: <CADPb22QhFJYyi_QFbDjvzpkRjz9Ddq_1Q9mgUVp_r+PP6i7Sfw@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 622 bytes --]
On Tuesday 20 March 2012 22:18:48 Doug Evans wrote:
> On Mon, Mar 19, 2012 at 5:48 PM, Mike Frysinger wrote:
> > i'd like to split up a ChangeLog to push arch-specific pieces into
> > subdirs rather than having the common ChangeLog be clogged with
> > non-common changes. is there a policy governing this ? or should i just
> > cut all the relevant pieces out of the common one and paste it into the
> > subdir and be done ?
>
> It kinda depends on what the owners want.
>
> You don't explicitly say you're talking about sim/, and it's not clear
> that's it.
yes, i'm talking about sim ChangeLogs
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-03-21 2:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 0:48 Mike Frysinger
2012-03-21 2:19 ` Doug Evans
2012-03-21 2:26 ` Mike Frysinger [this message]
2012-03-21 2:42 ` Doug Evans
2012-03-21 20:00 ` Stan Shebs
2012-03-23 3:25 ` Mike Frysinger
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=201203202226.46068.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=dje@google.com \
--cc=gdb@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