From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Doug Evans <dje@google.com>, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [patch] Create cleanups.[ch]
Date: Wed, 18 Apr 2012 04:26:00 -0000 [thread overview]
Message-ID: <m3hawh4x1g.fsf@redhat.com> (raw)
In-Reply-To: <20120417225417.GO2852@adacore.com> (Joel Brobecker's message of "Tue, 17 Apr 2012 15:54:17 -0700")
On Tuesday, April 17 2012, Joel Brobecker wrote:
>> > It should be:
>> >
>> > Copyright (C) 2012 Free Software Foundation, Inc.
>> >
>> > AFAIK, since it's a new file.
>>
>> I'm of two minds on this, but here I just "went with the flow."
>
> Have we considered the option of asking advice from the FSF about this?
> Then we'd have a definitive answer which we can record as well (put that
> in our CS guide, perhaps in gdbint.texi or in the Wiki). I've asked
> a couple of questions already this year, so I feel a little hesitant
> to ask myself (it's silly I know, just can't help it).
I can gladly ask :-). What's the e-mail/procedure? Should I Cc them in
this e-mail?
Thanks,
--
Sergio
next prev parent reply other threads:[~2012-04-18 2:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 20:27 Doug Evans
2012-04-16 7:27 ` Sergio Durigan Junior
2012-04-16 10:52 ` Pedro Alves
2012-04-16 19:11 ` Sergio Durigan Junior
2012-04-18 9:43 ` Pedro Alves
2012-04-19 17:37 ` Sergio Durigan Junior
2012-04-20 15:09 ` Pedro Alves
2012-04-16 20:06 ` Tom Tromey
2012-04-16 20:42 ` Pedro Alves
2012-04-16 20:59 ` Tom Tromey
2012-04-17 22:41 ` Doug Evans
2012-04-16 20:10 ` Tom Tromey
2012-04-17 22:54 ` Doug Evans
2012-04-17 22:59 ` Joel Brobecker
2012-04-18 4:26 ` Sergio Durigan Junior [this message]
2012-04-18 6:22 ` Joel Brobecker
2012-04-16 10:40 ` Pedro Alves
2012-04-18 14:02 ` Yao Qi
2012-04-18 14:32 ` Tom Tromey
2012-04-16 2:07 Doug Evans
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=m3hawh4x1g.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--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