Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Robert Dubner <rdubner@symas.com>
To: "Mark Wielaard" <mark@klomp.org>
Cc: <gdb@sourceware.org>
Subject: RE: Legal assigment forms for GDB
Date: Thu, 22 Feb 2024 17:26:46 -0600 (CST)	[thread overview]
Message-ID: <017301da65e6$9ac22870$d0467950$@symas.com> (raw)
In-Reply-To: <20240222213809.GE12488@gnu.wildebeest.org>

I appreciate your response and response and your advice.  And, yes, I made
the same request twice.  I have long since learned that in the world of
legalisms, words don't necessarily mean what I think they mean, so I have
a tendency to try to follow instructions as precisely as I can.  

Thanks very much,

Bob Dubner

-----Original Message-----
From: Mark Wielaard <mark@klomp.org> 
Sent: Thursday, February 22, 2024 16:38
To: Robert Dubner <rdubner@symas.com>
Cc: gdb@sourceware.org
Subject: Re: Legal assigment forms for GDB

Hi Bob,

On Thu, Feb 22, 2024 at 02:39:51PM -0600, Robert Dubner wrote:
> I anticipate making contributions to GDB on an ongoing basis.  
> Apparently there are forms the FSF wants filled out, and according to 
> https://sourceware.org/gdb/wiki/ContributionChecklist, I am supposed 
> to ask for them here.
> 
> I hereby request any forms I need.

I saw you made the same request for GCC. You can use the same
request-assign.future for both GCC and GDB:
https://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/Copyright/request-as
sign.future

Just say GCC and GDB under
[What is the name of the program or package you're contributing to?]

Then just sent a copy to assign@gnu.org

Cheers,

Mark

      reply	other threads:[~2024-02-22 23:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22 20:39 Robert Dubner
2024-02-22 21:38 ` Mark Wielaard
2024-02-22 23:26   ` Robert Dubner [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='017301da65e6$9ac22870$d0467950$@symas.com' \
    --to=rdubner@symas.com \
    --cc=gdb@sourceware.org \
    --cc=mark@klomp.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