From: Eli Zaretskii <eliz@gnu.org>
To: Charalampos Mitrodimas <charmitro@posteo.net>
Cc: 70139-done@debbugs.gnu.org
Subject: bug#70139: [PATCH] Improve key-translate to support removing translations
Date: Thu, 23 May 2024 16:25:04 +0300 [thread overview]
Message-ID: <86fru84q4v.fsf@gnu.org> (raw)
In-Reply-To: <m24jas5ibk.fsf@posteo.net> (message from Charalampos Mitrodimas on Mon, 20 May 2024 20:39:27 +0000)
> From: Charalampos Mitrodimas <charmitro@posteo.net>
> Cc: 70139@debbugs.gnu.org
> Date: Mon, 20 May 2024 20:39:27 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Charalampos Mitrodimas <charmitro@posteo.net>
> >> Date: Sun, 14 Apr 2024 21:31:37 +0000
> >> Cc: 70139@debbugs.gnu.org
> >>
> >> >
> >> > Charalampos, would you like to start the legal paperwork of assigning
> >> > to the FSF the copyright for your contributions? This contribution is
> >> > already slightly above the limit that we are allowed to accept without
> >> > a copyright assignment. If you agree, I will send you the form to
> >> > fill and the instructions to go with it.
> >>
> >> Yes I would like, as I’m planning to become more active as a contributor.
> >>
> >> Please send it over.
> >
> > Form sent off-list.
>
> Legal paperwork is now signed and countersigned by the Free Software
> Foundation.
Thanks, I therefore installed the changes on the master branch, and
I'm closing this bug.
next prev parent reply other threads:[~2024-05-23 13:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 9:50 bug#70139: 29.3.50; key-translate does not support all keyboard-translate usages Robert Pluim
2024-04-02 14:21 ` bug#70139: [PATCH] Improve key-translate to support removing translations Charalampos Mitrodimas
2024-04-02 14:28 ` bug#70139: 29.3.50; key-translate does not support all keyboard-translate usages Charalampos Mitrodimas
2024-04-02 15:41 ` Robert Pluim
2024-04-02 19:02 ` bug#70139: [PATCH] Improve key-translate to support removing translations Charalampos Mitrodimas
2024-04-04 13:00 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-04 19:48 ` Charalampos Mitrodimas
2024-04-04 21:53 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-06 17:09 ` Charalampos Mitrodimas
2024-04-06 17:18 ` Charalampos Mitrodimas
2024-04-07 14:45 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-09 11:14 ` Charalampos Mitrodimas
2024-04-09 12:57 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-09 13:07 ` Charalampos Mitrodimas
2024-04-13 9:19 ` Eli Zaretskii
2024-04-13 12:46 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-13 16:02 ` Eli Zaretskii
2024-04-14 21:31 ` Charalampos Mitrodimas
2024-04-15 2:30 ` Eli Zaretskii
2024-05-20 20:39 ` Charalampos Mitrodimas
2024-05-23 13:25 ` Eli Zaretskii [this message]
2024-04-04 12:27 ` bug#70139: 29.3.50; key-translate does not support all keyboard-translate usages Eli Zaretskii
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=86fru84q4v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70139-done@debbugs.gnu.org \
--cc=charmitro@posteo.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/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).