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

> 
> 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.

As they say, I am not a lawyer.  I can't comment on the validity of a 
letter when the digital signature of the attached files doesn't match. 
My gut reaction is to think it is not valid.

Move significantly, I think this need for letters is going to cause 
problems down the track.  Everytime an IBM employee tries to get a new 
non-trivial change into GDB another letter is required.  Everytime 
someone, not from IBM, posts a patch, and an IBM employee decides to 
significantly revise and then re-submit the change, another letter is 
required.

	Andrew



      reply	other threads:[~2001-08-17 10:06 UTC|newest]

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

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=3B7D4F15.2010007@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=ARENZ@de.ibm.com \
    --cc=DJBARROW@de.ibm.com \
    --cc=Ulrich.Weigand@de.ibm.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