all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Visuwesh <visuweshm@gmail.com>
Cc: 55393@debbugs.gnu.org
Subject: bug#55393: describe-keymap: suggest symbol at point
Date: Sun, 15 May 2022 09:19:08 +0300	[thread overview]
Message-ID: <83wnenjp2b.fsf@gnu.org> (raw)
In-Reply-To: <87k0anl52f.fsf@gmail.com> (message from Visuwesh on Sun, 15 May 2022 11:18:08 +0530)

> From: Visuwesh <visuweshm@gmail.com>
> Cc: eliz@gnu.org
> Date: Sun, 15 May 2022 11:18:08 +0530
> 
> [ஞாயிறு மே 15, 2022] Eli Zaretskii wrote:
> 
> > One nit for the future: please always mention the bug number, when
> > it's known, in the commit log message.  (I added it for you this
> > time.)
> >
> 
> Sorry, I keep forgetting about this.  I will make sure to remember 
> next time.
> [ BTW, there's no way to know what the bug number will be when I first
>   do M-x submit-emacs-patch, is there?  ]

No, there isn't.  (Some people first report the problem, and then post
the patch in a separate message, once they receive the response from
the bug tracker with the bug number, for this very reason.)  So for
the first submission you cannot put the number there.  However, for
the other submissions you can add it.





      reply	other threads:[~2022-05-15  6:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13  4:05 bug#55393: describe-keymap: suggest symbol at point Visuwesh
2022-05-13  5:24 ` Visuwesh
2022-05-13  6:23 ` Eli Zaretskii
2022-05-13  6:35   ` Visuwesh
2022-05-13  6:51     ` Eli Zaretskii
2022-05-13  7:42       ` Visuwesh
2022-05-13 12:06         ` Eli Zaretskii
2022-05-13 12:47           ` Visuwesh
2022-05-15  5:26             ` Eli Zaretskii
2022-05-15  5:48               ` Visuwesh
2022-05-15  6:19                 ` Eli Zaretskii [this message]

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=83wnenjp2b.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=55393@debbugs.gnu.org \
    --cc=visuweshm@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.