Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Hilfinger <hilfingr@EECS.Berkeley.EDU>
To: gdb-patches@sourceware.org
Subject: Re: Procedure for large drop?
Date: Mon, 15 Aug 2005 21:50:00 -0000	[thread overview]
Message-ID: <200508152119.j7FLJjSJ005656@tully.CS.Berkeley.EDU> (raw)
In-Reply-To: Message from Daniel Jacobowitz <drow@false.org>  of "Mon, 15 Aug 2005 09:37:09 EDT." <20050815133708.GA1460@nevyn.them.org>


> I'm of mixed minds as to whether this is necessary, but we do have a
> convenient place to put the file: ftp.sourceware.org/pub/gdb/contrib/.

Thanks. I'm not sure about this either, but 

1. The FSF is finicky about having documented assurances of code
   ownership (and rightly so).

2. HP's existing assignment agreement applies only to contributions 
   explicitly made by specific employees.

3. AdaCore does not own any of the code from which some of its planned
   submissions will derive; HP does.

So I conclude that some sort of symbolic act is needed so that AdaCore
will clearly be submitting mods to sources clearly assigned to the FSF.

Again, thanks for your help.

Paul Hilfinger


  reply	other threads:[~2005-08-15 21:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15 13:37 Paul Hilfinger
2005-08-15 14:15 ` Daniel Jacobowitz
2005-08-15 21:50   ` Paul Hilfinger [this message]
2005-08-16  2:36     ` Jason Molenda
2005-08-20 22:15   ` Paul Hilfinger
2005-08-22 19:00     ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2006-10-04 19:00 [patch] Pushing Inferior Function Arguments onto Stack on PowerPC64 machines janani
2006-10-04 19:11 ` Daniel Jacobowitz
2006-10-04 19:14   ` Daniel Jacobowitz
2006-10-04 20:19   ` Mark Kettenis
2006-10-04 20:27     ` Andreas Schwab
     [not found]   ` <OFE88464A1.C58B072A-ON872571FD.006ABA69-862571FD.006C7CFB@us.ibm.com>
2006-10-04 20:26     ` Daniel Jacobowitz
     [not found] <20041026075115.4A2C354AAB5@stray.canids>
     [not found] ` <20041026132924.GA26886@nevyn.them.org>
     [not found]   ` <drow@false.org>
2004-10-26 15:01     ` backtrace changes current source location Felix Lee
2004-10-27 17:35       ` Andrew Cagney
2004-10-27 17:40         ` Daniel Jacobowitz
2004-10-28  0:52         ` Felix Lee
2004-10-29 15:22           ` Andrew Cagney
2004-10-29 15:36             ` Daniel Jacobowitz
2004-10-29 22:07             ` Felix Lee
2004-10-30  0:02               ` Andrew Cagney
2004-10-30  3:28                 ` Felix Lee
2004-11-01  4:38                   ` Felix Lee
2004-11-01 16:04                     ` Andrew Cagney
2004-11-01 16:13                     ` Daniel Jacobowitz
2004-11-05  8:51     ` Felix Lee
2006-10-04 20:43     ` [patch] Pushing Inferior Function Arguments onto Stack on PowerPC64 machines David Edelsohn
2006-10-04 20:52       ` Daniel Jacobowitz

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=200508152119.j7FLJjSJ005656@tully.CS.Berkeley.EDU \
    --to=hilfingr@eecs.berkeley.edu \
    --cc=gdb-patches@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