From: Eli Zaretskii <eliz@gnu.org>
To: Konstantin Kharlamov <hi-angel@yandex.ru>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Documenting FSF copyright assignment process
Date: Tue, 16 Apr 2019 18:34:12 +0300 [thread overview]
Message-ID: <837ebuge17.fsf@gnu.org> (raw)
In-Reply-To: <1555362298.16927.0@yandex.ru> (message from Konstantin Kharlamov on Tue, 16 Apr 2019 00:04:58 +0300)
> Date: Tue, 16 Apr 2019 00:04:58 +0300
> From: Konstantin Kharlamov <hi-angel@yandex.ru>
> Cc: emacs-devel@gnu.org, rms@gnu.org
>
> I wonder, per discussion above, can a similar update be applied here
> https://www.gnu.org/software/emacs/manual/html_node/emacs/Copyright-Assignment.html#Copyright-Assignment
> ?
OK, I added a reference to the form there, thanks.
next prev parent reply other threads:[~2019-04-16 15:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 23:33 Documenting FSF copyright assignment process Konstantin Kharlamov
2019-04-11 13:21 ` [OFFTOPIC] " Stefan Monnier
2019-04-11 13:51 ` Eli Zaretskii
2019-04-11 14:00 ` Clément Pit-Claudel
2019-04-11 18:03 ` Paul Eggert
2019-04-11 19:08 ` Eli Zaretskii
2019-04-11 23:53 ` Stefan Monnier
2019-04-15 13:13 ` Phillip Lord
2019-04-15 14:23 ` Stefan Monnier
2019-04-15 17:05 ` Phillip Lord
2019-04-15 14:38 ` Eli Zaretskii
2019-04-11 23:49 ` Konstantin Kharlamov
2019-04-12 7:00 ` Eli Zaretskii
2019-04-12 8:57 ` Konstantin Kharlamov
2019-04-12 9:33 ` Eli Zaretskii
2019-04-12 9:42 ` Konstantin Kharlamov
2019-04-12 12:33 ` Eli Zaretskii
2019-04-15 21:04 ` Konstantin Kharlamov
2019-04-16 15:34 ` Eli Zaretskii [this message]
2019-04-16 18:03 ` Konstantin Kharlamov
2019-04-16 18:28 ` Eli Zaretskii
2019-04-16 18:55 ` Konstantin Kharlamov
2019-04-16 19:11 ` Eli Zaretskii
2019-04-16 19:18 ` Konstantin Kharlamov
2019-04-16 19:24 ` Eli Zaretskii
2019-04-16 19:29 ` Konstantin Kharlamov
2019-04-17 2:33 ` Eli Zaretskii
2019-04-12 17:30 ` Amin Bandali
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=837ebuge17.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=hi-angel@yandex.ru \
--cc=rms@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.