From: Sergey Bugaev <bugaevc@gmail.com>
To: Michael Banck <mbanck@gmx.net>
Cc: guix-devel@gnu.org, Damien Zammit <damien@zamaudio.com>,
bug-hurd <bug-hurd@gnu.org>
Subject: Re: Regarding copyright assignment to FSF
Date: Sat, 14 Aug 2021 12:00:55 +0300 [thread overview]
Message-ID: <CAN9u=HcNzTooEzPu7Hddk-=rozn7jMzLBGM=0Y3qAOwM+Q-Lcw@mail.gmail.com> (raw)
In-Reply-To: <6117580d.1c69fb81.7b243.1c35@mx.google.com>
On Sat, Aug 14, 2021 at 8:43 AM Michael Banck <mbanck@gmx.net> wrote:
> The fact that this process potentially or apparently took (or rather,
> has been taking) months for Sergey (I don't know when it was initiated),
> is a pretty good indicator that it is more than a nuisance.
Well, this is partly my own fault: I've been postponing trying to scan
the signed papers (I can hack on kernel internals alright, but ask me
to deal with a scanner and I'm lost). But that being said, the FSF has
also been consistently slow to respond, so it would take months even
if I had done everything promptly.
Sergey
next prev parent reply other threads:[~2021-08-15 13:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210810020240.wpd5pksgdh5e2e3u@begin>
2021-08-10 4:55 ` Fwd: Hurd Security vulnerabilities, please upgrade! jbranso
2021-08-10 15:52 ` Ricardo Wurmus
2021-08-10 15:56 ` Samuel Thibault
2021-08-11 13:01 ` Ludovic Courtès
2021-08-12 2:18 ` Regarding copyright assignment to FSF Damien Zammit
2021-08-13 13:42 ` Maxime Devos
2021-08-13 16:23 ` Samuel Thibault
2021-08-14 21:26 ` Svante Signell
2021-08-14 21:40 ` Samuel Thibault
2021-08-13 20:48 ` Dr. Arne Babenhauserheide
2021-08-14 3:42 ` Ivan Shmakov
2021-08-14 5:43 ` Michael Banck
2021-08-14 9:00 ` Sergey Bugaev [this message]
2021-08-14 12:19 ` Dr. Arne Babenhauserheide
2021-08-14 13:12 ` Michael Banck
2021-08-14 14:16 ` Akib Azmain Turja
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN9u=HcNzTooEzPu7Hddk-=rozn7jMzLBGM=0Y3qAOwM+Q-Lcw@mail.gmail.com' \
--to=bugaevc@gmail.com \
--cc=bug-hurd@gnu.org \
--cc=damien@zamaudio.com \
--cc=guix-devel@gnu.org \
--cc=mbanck@gmx.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).