From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: RISC OS port
Date: Fri, 26 Nov 2004 13:57:28 +0100 [thread overview]
Message-ID: <200411261357.29602.okuji@enbug.org> (raw)
In-Reply-To: <87sm6wrk0a.fsf@marco.marco-g.com>
On Friday 26 November 2004 11:18, Marco Gerards wrote:
> > include/grub/arm/linux_setup.h is an unmodified file from Linux
> > 2.6.9 (include/asm-arm/setup.h).
>
> IIRC copyright need to be assigned to the FSF for every change/file.
> Okuji, how should we deal with such things?
http://www.gnu.org/prep/maintain/html_node/External-Libraries.html#External-Libraries
Okuji
next prev parent reply other threads:[~2004-11-26 13:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 17:00 RISC OS port Timothy Baldwin
2004-11-23 18:03 ` Marco Gerards
2004-11-26 0:47 ` Timothy Baldwin
2004-11-26 10:18 ` Marco Gerards
2004-11-26 12:57 ` Yoshinori K. Okuji [this message]
2004-11-27 1:36 ` Timothy Baldwin
2004-11-27 18:21 ` Timothy Baldwin
2004-12-03 13:07 ` Marco Gerards
2004-12-04 10:30 ` Timothy Baldwin
2004-12-29 19:46 ` Marco Gerards
2004-12-03 12:53 ` Marco Gerards
2004-12-03 13:51 ` Johan Rydberg
2004-12-04 10:27 ` Timothy Baldwin
2004-12-04 13:14 ` Marco Gerards
-- strict thread matches above, loose matches on Subject: below --
2013-05-03 11:49 Vladimir 'φ-coder/phcoder' Serbinenko
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=200411261357.29602.okuji@enbug.org \
--to=okuji@enbug.org \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.