From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: consolidate ELF header checks
Date: Tue, 8 Feb 2005 13:54:01 +0100 [thread overview]
Message-ID: <200502081354.01411.okuji@enbug.org> (raw)
In-Reply-To: <20050206212812.GA25570@zulo.hadrons.org>
On Sunday 06 February 2005 22:28, Guillem Jover wrote:
> Sorry about that, it was not intentional. You asked Marco and he
> replied so I though that was enough, then I sent the patch revision
> Marco asked and left home, didn't saw your other mails until today.
It's okay. Don't mind. I just want to make things clear.
> I was hacking on the kFreeBSD loader for GRUB Legacy and needed
> other copyright assignments for other GNU projects, so I asked for
> GRUB as well. Marco or Jeff pointed me to the assignment procudures.
I need to know how you did precisely. Did you ask assign@gnu.org or
something else? What template did you use? Did any maintainer of GNU
Software specify how to proceed it?
BTW, please contact appropriate maintainers before trying to assign
copyright from now on. Maintainers of GNU Software are responsible for
managing copyright issues. If you bypass the maintainers, they may not
keep things consistent, since they are not notified even if the
procedures are wrong.
For example, I am very afraid that you might have used an obsolete
request form. The FSF revises the request form and even the whole
procedures from time to time, so you need to request up-to-date
information when you assign copyright.
Another - more serious - case is that you might have ignored the first
request completely and simply sent a filled assignment paper to the
FSF. You could do this, if you get a copy from someone who has assigned
copyright. If this happens, you wouldn't be informed of all the
cautions by the FSF, such as a copyright disclaimer by your employer.
Okuji
next prev parent reply other threads:[~2005-02-08 13:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 4:47 consolidate ELF header checks Guillem Jover
2005-02-01 19:26 ` Marco Gerards
2005-02-04 22:25 ` Marco Gerards
2005-02-04 22:40 ` Yoshinori K. Okuji
2005-02-05 14:10 ` Marco Gerards
2005-02-05 22:55 ` Yoshinori K. Okuji
2005-02-05 22:45 ` Guillem Jover
2005-02-06 11:02 ` Marco Gerards
2005-02-06 12:58 ` Yoshinori K. Okuji
2005-02-06 14:22 ` Marco Gerards
2005-02-06 21:28 ` Guillem Jover
2005-02-08 12:54 ` Yoshinori K. Okuji [this message]
2005-02-09 7:10 ` Guillem Jover
2005-02-10 19:21 ` Yoshinori K. Okuji
2005-02-11 17:25 ` Marco Gerards
2005-02-11 18:07 ` Yoshinori K. Okuji
2005-02-11 18:24 ` Marco Gerards
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=200502081354.01411.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.