Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: "Manu" <manubee@wanadoo.fr>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Configure GDB for MinGW
Date: Wed, 26 May 2004 10:41:00 -0000	[thread overview]
Message-ID: <1438-Wed26May2004133824+0300-eliz@gnu.org> (raw)
In-Reply-To: <20040526022749.GA25725@coe.bosbc.com>

> Date: Tue, 25 May 2004 22:27:49 -0400
> From: Christopher Faylor <cgf@alum.bu.edu>
> 
> >I've been managing a project for two or three years, I created the
> >application under the GNU GPL and its library under the public domain.
> >I'm supporting both Free Software and Open Source.  Then, I think you
> >can trust what I'm providing.  IMO, It is more valuable than any paper.
> 
> Judging your reputation isn't really an option for me.

Signing papers is not about the reputation of the person who
contributes; in fact, it has nothing to do with that at all.  It is
required for the GNU project to be able to defend in court its legal
right to distribute every single line of the code in its projects, in
the (arguably improbable) case that some software vendor will try to
claim that part of the GDB code was unlawfully stolen from that
software vendor.

For example, your employer could claim that code you contributed to
GDB was written when you were working for that employer and that
therefore that code is your employer's property, and the FSF has no
right to distribute it.


  reply	other threads:[~2004-05-26 10:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-21 10:05 Manu
2004-05-24 17:36 ` Mark Kettenis
2004-05-24 21:01   ` Christopher Faylor
2004-05-25 21:32     ` Manu
2004-05-26  2:27       ` Christopher Faylor
2004-05-26 10:41         ` Eli Zaretskii [this message]
2004-05-25 21:32   ` Manu

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=1438-Wed26May2004133824+0300-eliz@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=manubee@wanadoo.fr \
    /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