From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Baums <baums@stefanbaums.com>
Cc: 55539@debbugs.gnu.org
Subject: bug#55539: 28.1; Support for the Kharoṣṭhī Script
Date: Tue, 31 May 2022 16:47:28 +0300 [thread overview]
Message-ID: <83czftizkf.fsf@gnu.org> (raw)
In-Reply-To: <87fsl4m8e3.fsf@stefanbaums.com> (message from Stefan Baums on Fri, 20 May 2022 19:16:52 +0200)
> From: Stefan Baums <baums@stefanbaums.com>
> Cc: 55539@debbugs.gnu.org
> Date: Fri, 20 May 2022 19:16:52 +0200
>
> > Would you be willing to start the legal paperwork of the
> > copyright assignment at this time? If yes, I will send you the
> > form to fill and the instructions to email the form.
>
> I was dreading that process, but am willing. Yes, please send me
> the forms.
Your copyright assignment paperwork is now complete, so we can install
this. Would you mind to post an up-to-date patch, incorporating all
the comments and discussions we had, relative to the current
development sources?
Thanks.
next prev parent reply other threads:[~2022-05-31 13:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 9:48 bug#55539: 28.1; Support for the Kharoṣṭhī Script Stefan Baums
2022-05-20 16:18 ` Eli Zaretskii
2022-05-20 17:16 ` Stefan Baums
2022-05-20 17:27 ` Eli Zaretskii
2022-05-20 18:05 ` Stefan Baums
2022-05-31 13:47 ` Eli Zaretskii [this message]
2022-06-05 16:55 ` Stefan Baums
2022-06-05 16:58 ` Eli Zaretskii
2022-06-05 17:18 ` Stefan Baums
2022-06-05 17:52 ` समीर सिंह Sameer Singh
2022-06-05 18:45 ` Stefan Baums
2022-06-08 13:29 ` समीर सिंह Sameer Singh
2022-06-08 18:42 ` Stefan Baums
2022-06-09 4:59 ` Eli Zaretskii
2022-06-09 9:40 ` Stefan Baums
2022-06-09 10:17 ` Eli Zaretskii
2022-06-09 9:14 ` Eli Zaretskii
2022-06-09 9:52 ` Stefan Baums
2022-06-09 9:56 ` Stefan Baums
2022-06-09 10:29 ` Eli Zaretskii
2022-06-09 10:37 ` Stefan Baums
2022-05-20 17:26 ` Stefan Baums
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83czftizkf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=55539@debbugs.gnu.org \
--cc=baums@stefanbaums.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).