From: Robert Pluim <rpluim@gmail.com>
To: "प्रद्युम्न परांजपे" <pradyparanjpe@gmail.com>
Cc: Jeremy Bryant <jb@jeremybryant.net>,
Justin Burkett <justin@burkett.cc>,
71718@debbugs.gnu.org
Subject: bug#71718: Unicode symbols to represent which key special keys, bug#71718: Unicode symbols to represent which key special keys
Date: Fri, 28 Jun 2024 09:40:07 +0200 [thread overview]
Message-ID: <87bk3la52g.fsf@gmail.com> (raw)
In-Reply-To: <CABt=8ObbJfR=s9xkk0x71T_7GzbpGMYh+HD=tOt+=P7RqS_jNQ@mail.gmail.com> ("प्रद्युम्न परांजपे"'s message of "Fri, 28 Jun 2024 11:43:58 +0530")
>>>>> On Fri, 28 Jun 2024 11:43:58 +0530, प्रद्युम्न परांजपे <pradyparanjpe@gmail.com> said:
Prady> I am unaware of the protocol here.
Prady> I submitted the PR as a bug as advised by the owner of the repository on
Prady> github.
Prady> I agree with, and accept both suggestions (from Robert and Jeremy).
Prady> How do I proceed with including the suggestions?
Change your code to match the suggestions, ensure that all the changes
are in 1 commit, then reply to this email with the file produced by
git format-patch -1
as an attachment. See "** Getting involved with development" in
CONTRIBUTE in the emacs sources for more info.
Prady> I am afraid I, being ignorant, might end up opening multiple bug reports
Prady> messing up things.
Prady> So I am not actively doing anything right now.
Prady> Please guide me through.
As long as you just reply to '71718@debbugs.gnu.org' and the other
people in the email headers, you wonʼt end up creating multiple
reports.
Robert
--
next prev parent reply other threads:[~2024-06-28 7:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-22 9:01 bug#71718: Unicode symbols to represent which key special keys प्रद्युम्न परांजपे
2024-06-22 18:17 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-23 15:29 ` bug#71718: Unicode symbols to represent which key special keys, " Robert Pluim
2024-06-28 6:13 ` प्रद्युम्न परांजपे
2024-06-28 7:40 ` Robert Pluim [this message]
2024-06-28 17:59 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87bk3la52g.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=71718@debbugs.gnu.org \
--cc=jb@jeremybryant.net \
--cc=justin@burkett.cc \
--cc=pradyparanjpe@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.
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.