From: Daniel Jacobowitz <drow@false.org>
To: Tom Tromey <tromey@redhat.com>
Cc: "Tedeschi, Walfred" <walfred.tedeschi@intel.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix display of structures/bitfields in register description.
Date: Mon, 29 Apr 2013 14:23:00 -0000 [thread overview]
Message-ID: <CAN9gPaE+u63cCBX3kmo=WosPbQQNcuP4O9od7LHaVQTDuUAw1g@mail.gmail.com> (raw)
In-Reply-To: <87fvyek9ec.fsf@fleche.redhat.com>
They have a different header because they're supposed to be embedded
in things that run on the target which are not necessarily
GPL-compatible. I figured out with the FSF what an appropriate notice
would be for that case. I'd generally rather we use that notice for
all target XML files, even in the testsuite, to prevent someone
copying the GPL'd version into something by accident - not a big deal,
though.
On Thu, Apr 25, 2013 at 9:49 AM, Tom Tromey <tromey@redhat.com> wrote:
> Walfred> Copyrights:
> Walfred> I took a look on several xml files and all of them had the same
> Walfred> copyright I have used. Though, would you recommend to use the
> Walfred> common GPL header?
>
> I don't know why the other .xml files have this other header.
> However, seeing as the new file is in the test suite, I think the plain
> GPL comment is preferable.
>
> Tom
--
Thanks,
Daniel
next prev parent reply other threads:[~2013-04-28 22:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 17:30 Walfred Tedeschi
2013-04-24 20:50 ` Tom Tromey
2013-04-25 16:18 ` Tedeschi, Walfred
2013-04-25 19:35 ` Tom Tromey
2013-04-25 19:39 ` Tedeschi, Walfred
2013-04-29 14:23 ` Daniel Jacobowitz [this message]
2013-04-29 19:56 ` Tom Tromey
2013-04-29 20:24 ` Tedeschi, Walfred
2013-04-30 7:27 ` Tom Tromey
2013-04-25 19:50 Walfred Tedeschi
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='CAN9gPaE+u63cCBX3kmo=WosPbQQNcuP4O9od7LHaVQTDuUAw1g@mail.gmail.com' \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
--cc=walfred.tedeschi@intel.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