public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bruce Korb <bruce.korb@gmail.com>
To: Bruce Korb <bruce.korb@gmail.com>,
	"Joseph S. Myers" <joseph@codesourcery.com>,
		Jakub Jelinek <jakub@redhat.com>,
	Andrew Pinski <pinskia@gmail.com>,
	gcc-patches@gcc.gnu.org, 	rdsandiford@googlemail.com
Subject: Re: [committed] 2011 and 2012 Copyright year updates
Date: Mon, 07 Jan 2013 20:30:00 -0000	[thread overview]
Message-ID: <CAKRnqNLoTnPYE3E1o9bh_FJaKh+hQh8keycBp05P8t07HKSb-g@mail.gmail.com> (raw)
In-Reply-To: <87mwwk4uc9.fsf@talisman.default>

HI,

On Mon, Jan 7, 2013 at 12:21 PM, Richard Sandiford
<rdsandiford@googlemail.com> wrote:
> It was just a question of whether to submit the fixincludes/ and gcc/
> parts as one patch (as I'd originally done) or as two separate patches.
> Two separate patches probably makes more sense and I think is what
> Joseph was suggesting.

In that case, I completely do not care at all which way it happens.
The effect is the same and the difference is as inconsequential as I
can imagine. :)
Thanks! - Bruce

  reply	other threads:[~2013-01-07 20:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-04 12:54 Jakub Jelinek
2013-01-04 16:44 ` Andrew Pinski
2013-01-04 16:49   ` Jakub Jelinek
2013-01-06 12:14     ` Richard Sandiford
2013-01-06 12:44       ` Jakub Jelinek
2013-01-06 21:48         ` Richard Sandiford
2013-01-07  8:56         ` Richard Biener
2013-01-06 20:24       ` Mike Stump
2013-01-06 20:37         ` Mike Stump
2013-01-06 21:53         ` Richard Sandiford
2013-01-07 16:00       ` Joseph S. Myers
2013-01-07 19:49         ` Richard Sandiford
2013-01-07 19:59           ` Bruce Korb
2013-01-07 20:22             ` Richard Sandiford
2013-01-07 20:30               ` Bruce Korb [this message]
2013-01-07 20:31           ` Joseph S. Myers
2013-01-08 20:49             ` Richard Sandiford
2013-01-10 14:17               ` Jakub Jelinek

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=CAKRnqNLoTnPYE3E1o9bh_FJaKh+hQh8keycBp05P8t07HKSb-g@mail.gmail.com \
    --to=bruce.korb@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=pinskia@gmail.com \
    --cc=rdsandiford@googlemail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).