From: Thomas Richter <thor@mail.math.tu-berlin.de>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: [BUG] Tab Expansion for C++
Date: Mon, 19 Feb 2007 11:48:00 -0000 [thread overview]
Message-ID: <200702190943.l1J9hQjj004616@mersenne.math.TU-Berlin.DE> (raw)
In-Reply-To: <20070214120436.GA27648@caradoc.them.org>
Hi again,
> > Could you provide some details on this? My impression is that gdb is GPL,
> > and as soon as I agree on this, we're ready to go?
>
> No, see http://www.gnu.org/licenses/why-assign.html. This is
> something quite different; it's a document that you'll have to sign,
> and possibly another one that your employer would also, depending on
> circumstances.
>
> It's an inconenience for new contributors, but sufficiently important
> to the FSF that we insist on it.
All fine, but *which* document would need to be signed? Is there a template
of sorts you can provide? The page above doesn't seem to provide details
on this.
Furthermore, I cannot develop under US copyright law. I can only develop
under German copyright law, which is again different. I can hand you the
copyright, but according to German law, I still have rights as the creator
of an entity that I cannot transfer to other people. (German: Urheberrecht)
It doesn't give me any major rights, though (as, it doesn't include the
right to copy the work, which is part of the copyright.).
Folks, that's getting ridiculously complicated... I don't want to contact
a lawer just to provide a patch. I really don't care - I just want a usable
gdb, that's all.
So long,
Thomas
next prev parent reply other threads:[~2007-02-19 9:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 16:28 Thomas Richter
2007-02-13 16:56 ` Daniel Jacobowitz
2007-02-13 17:08 ` Thomas Richter
2007-02-13 19:33 ` Daniel Jacobowitz
2007-02-14 12:08 ` Thomas Richter
2007-02-14 12:36 ` Daniel Jacobowitz
2007-02-19 11:48 ` Thomas Richter [this message]
2007-02-19 12:28 ` Daniel Jacobowitz
2007-02-19 13:03 ` Robert Dewar
2007-02-13 19:00 ` Andreas Schwab
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=200702190943.l1J9hQjj004616@mersenne.math.TU-Berlin.DE \
--to=thor@mail.math.tu-berlin.de \
--cc=drow@false.org \
--cc=gdb@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox