Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Denis Joseph Barrow" <DJBARROW@de.ibm.com>
To: ac131313@cygnus.com, "Ulrich Weigand" <Ulrich.Weigand@de.ibm.com>,
	"Christoph Arenz" <ARENZ@de.ibm.com>
Cc: gdb-patches@sourceware.cygnus.com,
	"Wolfgang Bezold" <bezold1@de.ibm.com>
Subject: re gdb patches
Date: Fri, 17 Aug 2001 03:50:00 -0000	[thread overview]
Message-ID: <OFDDEE2775.7B65797F-ONC1256AAB.003A409F@de.ibm.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]

Hi Andrew,

>As things stand, the FSF doesn't own this code and, as a consequence,
>people have strong reservations about working on it.  (IBM will only
>assign the copyright using a letter that cites a digitally signed patch.
>I understand this process to be slow and complicated.).

The last one time software letter we sent was a few months back & not
against
the latest patches, with the aggreement that we send the letter when the
patch was
close to integration.

We currently plan to send another one-time letter with this patch,it is
difficult
getting our legal guys to aggree to a future assignment form.
Does the FSF have problems with our one time letters, is it primarily that
the patches
are digitally signed & this means they are invalid as soon as I send
another attempted
patch for integration.



D.J. Barrow Gnu/Linux for S/390 kernel developer
eMail: djbarrow@de.ibm.com,barrow_dj@yahoo.com
Phone: +49-(0)7031-16-2583
IBM Germany Lab, Schönaicherstr. 220, 71032 Böblingen


             reply	other threads:[~2001-08-17  3:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-17  3:50 Denis Joseph Barrow [this message]
2001-08-17 10:06 ` Andrew Cagney

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=OFDDEE2775.7B65797F-ONC1256AAB.003A409F@de.ibm.com \
    --to=djbarrow@de.ibm.com \
    --cc=ARENZ@de.ibm.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=ac131313@cygnus.com \
    --cc=bezold1@de.ibm.com \
    --cc=gdb-patches@sourceware.cygnus.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