Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@alum.bu.edu>
To: gdb-patches@sources.redhat.com
Subject: Re: Configure GDB for MinGW
Date: Wed, 26 May 2004 02:27:00 -0000	[thread overview]
Message-ID: <20040526022749.GA25725@coe.bosbc.com> (raw)
In-Reply-To: <001101c442a1$77545580$4619fdc1@ftiy9yhq97>

On Tue, May 25, 2004 at 11:43:42PM +0200, Manu wrote:
>Christopher Faylor wrote:
>
>> On Mon, May 24, 2004 at 07:36:51PM +0200, Mark Kettenis wrote:
>> >   From: "Manu"
>> >   Date: Fri, 21 May 2004 12:04:20 +0200
>> >
>> >Thanks for your contribution.  I think it is small enough to be
>> >accepted without a copyright assignment, especially if you follow the
>> >advice below.  I'm not completely sure though.
>>
>> I guess we'd have to see the actual finished patch but given that it makes
>> changes to a number of files and adds new functionality, I don't think
>> it really could be considered trivial.
>
>Is it true that the FSF sometimes accepts a disclaimer instead of a
>copyright assignment?

I believe they do sometimes.

>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.  I work for TimeSys.
If you want to take up the matter with the FSF and let me know what they
think I can wait for that.  The paperwork isn't that odious and signing
it would mean that you can make future hassle-free contributions to gdb.

In the meantime, I'll wait on your patch.  Maybe it really could be
considered trivial.  We could always get a ruling from Andrew.  It still
seems like the best long term solution would be to get the assignment
in with the FSF, though.

I'm not quite sure how you could do the cygming stuff that I mentioned
in a patch but if you just supply patches against cygwin named files,
and use cygming in the configuration, I'll figure things out somehow.

cgf


  reply	other threads:[~2004-05-26  2:27 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 [this message]
2004-05-26 10:41         ` Eli Zaretskii
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=20040526022749.GA25725@coe.bosbc.com \
    --to=cgf@alum.bu.edu \
    --cc=gdb-patches@sources.redhat.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