From: "Frank Ch. Eigler" <fche@elastic.org>
To: woodzltc zhou <woodzltc@gmail.com>
Cc: overseers@sourceware.org
Subject: Re: Lost my public key and how to reconnect
Date: Sun, 06 May 2012 18:37:00 -0000 [thread overview]
Message-ID: <20120506183642.GG32489@elastic.org> (raw)
In-Reply-To: <CALeG9p_bSpgfQ29Yhe6+DUrtH2DHRgrMEsb26_kydhcoJi8FSQ@mail.gmail.com>
Hi -
> I was working on GDB (GNU debugger) as a maintainer from 2005 to
> 2007 when I was working at IBM Linux Technology Center. I am now
> thinking of connecting back to GDB development as an individual
> contributor. Could you please tell me how should I proceed? [...]
The first step is probably checking what sort of copyright assignment
you have on file at the FSF. It's possible that your old
contributions were covered under an IBM blanket agreement, which
sounds like it would not apply to you any more. So work with gdb
maintainers to get that cleared up.
- FChE
prev parent reply other threads:[~2012-05-06 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-06 18:33 woodzltc zhou
2012-05-06 18:37 ` Frank Ch. Eigler [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=20120506183642.GG32489@elastic.org \
--to=fche@elastic.org \
--cc=overseers@sourceware.org \
--cc=woodzltc@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).