All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Grub for ia64
Date: Thu, 28 Sep 2006 15:38:50 +0200	[thread overview]
Message-ID: <87ven81579.fsf@xs4all.nl> (raw)
In-Reply-To: <87hcys9k6r.fsf@night.trouble.net> (Johan Rydberg's message of "Thu, 28 Sep 2006 15:47:56 +0200")

Johan Rydberg <jrydberg@night.trouble.net> writes:

> First a few legal comments.  I poked through the patches, and it seems
> that there are a few files that are copyrighted by Hewlett-Packard and
> David Mosberger-Tang.  All developers of GNU GRUB has agreed to sign
> over their copyright to FSF, so brining non-FSF copyrighted code into
> the project is a problem (and likely a show-stopper).

If code from third parties is used it will be a show stopper,
especially in such cases.

> There are also a few files that are released under LGPL.  Maintainers,
> are there any problems with bringing such files into GNU GRUB?

What do you mean by that?  Code written for the IA64 port or brought
in from elsewhere?

> Have you signed over copyright to FSF for your work on GNU GRUB? In
> other words, have you sent in an assignment record to FSF?  If not,
> let us know and we'll send you a request record.

Okuji or me will talk to contributors off-list usually about such
issues, so that won't be a problem.

> Anyhow, when I get a few more minutes over I'll try to review your
> patches more in depth.  

Thanks a lot for doing this!

> I do not know if there is a policy for how to contribute code to GRUB,
> but please send unified diffs (-u) instead of context diffs (-c).  I
> at least find them easier to read.

Like mentioned in the other emails, I want unified diffs (diff -up)
inlined in the email with a Changelog entry.  This is correctly picked
up in the patch in the other thread so I am confident it will work out
fine for the port as well. :-)

--
Marco
 




  parent reply	other threads:[~2006-09-28 13:31 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-28 11:41 Grub for ia64 tgingold
2006-09-28 13:06 ` bibo,mao
2006-09-28 13:12   ` tgingold
2006-09-28 13:33 ` Marco Gerards
2006-09-28 13:45   ` tgingold
2006-09-28 14:29     ` Marco Gerards
2006-09-28 14:49       ` tgingold
2006-09-29  5:10     ` Grub for ia64 - function descriptors Hollis Blanchard
2006-09-29  6:59       ` tgingold
2006-09-29 13:16         ` Hollis Blanchard
2006-10-02  6:31           ` tgingold
2006-10-03  2:17             ` Hollis Blanchard
2006-10-03  4:04               ` tgingold
2006-10-03 15:09                 ` Hollis Blanchard
2006-09-28 13:47 ` Grub for ia64 Johan Rydberg
2006-09-28 13:35   ` tgingold
2006-09-28 14:15     ` Johan Rydberg
2006-09-28 13:38   ` Marco Gerards [this message]
2006-10-10 18:15   ` Johan Rydberg
2006-10-10 22:03     ` Jeff Bailey
2006-10-11 11:19       ` Johan Rydberg
2006-10-11 10:50     ` Tristan Gingold
  -- strict thread matches above, loose matches on Subject: below --
2006-10-11 11:43 Mao, Bibo
2006-10-12  8:21 ` Tristan Gingold
2006-10-12 11:30   ` Johan Rydberg
2006-10-12 11:35     ` Tristan Gingold
2006-10-12 12:11       ` Johan Rydberg
2006-10-12 14:14         ` Tristan Gingold
2006-10-12 15:32           ` Johan Rydberg
2006-10-13  5:22             ` Tristan Gingold
2006-10-13  8:02               ` bibo,mao
2006-10-13 18:48                 ` Yoshinori K. Okuji
2006-10-12 12:50 Mao, Bibo

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=87ven81579.fsf@xs4all.nl \
    --to=mgerards@xs4all.nl \
    --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.