From: Doug Evans <dje@google.com>
To: Scott Goldman <scottjg@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Phil Muldoon <pmuldoon@redhat.com>,
"eliz@gnu.org" <eliz@gnu.org>,
"copyright-clerk@fsf.org" <copyright-clerk@fsf.org>
Subject: Re: [PATCH] Allow user-defined as a category for python gdb macros (resend)
Date: Tue, 28 Feb 2012 07:51:00 -0000 [thread overview]
Message-ID: <CADPb22RBt2C5f=TSLor6AMKVAReAJ73ravVimuxFK3+A6cDvqQ@mail.gmail.com> (raw)
In-Reply-To: <03E840D17E263A48A5766AD576E0423A03DAC7799D@exch-mbx-111.vmware.com>
Ah. If the patch falls under the "no assignment needed" rule, awesome.
It is a (relatively) small patch, but I'm a bit shy at making such
calls (beyond the trivial cases).
On Mon, Feb 27, 2012 at 5:36 PM, Scott Goldman <scottjg@vmware.com> wrote:
> Hi Doug.
>
>> I'm happy to check it in for you.
>> Doing a final sanity check, there doesn't seem to be a copyright
>> assignment on file (in the place where gdb developers look to confirm
>> such things).
>> [Presumably it's cleared, but just hasn't been recorded yet.]
>> Can you double check to make sure the copyright assignment has gone
>> through.
>> Thanks!
>> [And sorry for the trouble.]
>
> My understanding is that VMware had some sort of issue with the assignment paperwork, but made an agreement with the FSF to release this patch in the public domain. Donald Robertson, one of the lawyers at the FSF, OK'ed this.
>
> I cc'ed the contact email I have for the fsf copyright assignment folks for Donald to confirm.
>
> -sjg
>
>
>> -----Original Message-----
>> From: Donald R Robertson III via RT [mailto:______@fsf.org]
>> Sent: Wednesday, November 09, 2011 7:27 AM
>> To: Krystia Przepiorski; Scott Goldman
>> Subject: [gnu.org #697202] copyright assignment form request for Scott
>> J. Goldman
>>
>> > [_______@vmware.com - Tue Nov 08 17:55:49 2011]:
>> >
>> > Donald - Sorry for the delay.
>> >
>> > Would it be acceptable to the FSF if VMware marked/released our
>> > contribution to the public domain when sending to you?
>> >
>> > Given that this is only 3-4 lines of code it is likely not worth
>> digging
>> > into modifying the Assignment Agreement.
>>
>> Ah, yes, there's no need for assignment in this situation. Thank you so
>> much for your time.
>>
>> >
>> > Thanks,
>> > Krystia
>> >
>> >
>> >
>> > Krystia Przepiorski | Associate Corporate Counsel | VMware, Inc. |
>> 3401
>> > Hillview Avenue, Palo Alto, CA 94304
>> >
>> >
>> >
>> >
>> >
>> > On 11/1/11 8:16 AM, "Donald R Robertson III via RT"
>> > <_______@fsf.org> wrote:
>> >
>> > >Hello again,
>> > >
>> > >I just wanted to check in on this issue. Were there any questions
>> about
>> > >our standard assignment
>> > >form? Thank you so much for your time, and I hope to hear from you
>> soon.
>> > >
>> > >--
>> > >Sincerely,
>> > >
>> > >Donald R. Robertson, III, J.D.
>> > >Assignment Administrator
>> > >Free Software Foundation
>> > >51 Franklin Street, Fifth Floor
>> > >Boston, MA 02110
>> > >
>> > >---
>> > >
>> >
>> >
>> >
>> >
>> --
>> Sincerely,
>>
>> Donald R. Robertson, III, J.D.
>> Assignment Administrator
>> Free Software Foundation
>> 51 Franklin Street, Fifth Floor
>> Boston, MA 02110
>>
>> ---
>
next prev parent reply other threads:[~2012-02-28 4:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 0:49 Scott Goldman
2012-02-14 3:12 ` Doug Evans
2012-02-14 7:57 ` Scott Goldman
2012-02-14 18:09 ` Eli Zaretskii
2012-02-14 20:19 ` Doug Evans
2012-02-14 12:48 ` Phil Muldoon
2012-02-15 9:27 ` Scott Goldman
2012-02-16 14:23 ` Phil Muldoon
2012-02-16 17:16 ` Eli Zaretskii
2012-02-23 3:03 ` Doug Evans
2012-02-23 3:32 ` Scott Goldman
2012-02-23 4:24 ` Eli Zaretskii
2012-02-23 5:13 ` Scott Goldman
2012-02-23 6:03 ` Doug Evans
2012-02-23 6:56 ` Scott Goldman
2012-02-23 8:21 ` Scott Goldman
2012-02-24 23:49 ` Scott Goldman
2012-02-28 1:36 ` Doug Evans
2012-02-28 4:18 ` Scott Goldman
2012-02-28 7:51 ` Doug Evans [this message]
2012-02-29 0:45 ` [doc RFA] " Doug Evans
2012-02-29 4:17 ` Eli Zaretskii
2012-03-01 19:31 ` Doug Evans
2012-03-01 20:26 ` Keith Seitz
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='CADPb22RBt2C5f=TSLor6AMKVAReAJ73ravVimuxFK3+A6cDvqQ@mail.gmail.com' \
--to=dje@google.com \
--cc=copyright-clerk@fsf.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@redhat.com \
--cc=scottjg@vmware.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