all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Theodor Thornhill via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 59252-done@debbugs.gnu.org, stefankangas@gmail.com, joaotavora@gmail.com
Subject: bug#59252: 29.0.50; Add new ts-modes to eglot-server-programs
Date: Sun, 27 Nov 2022 08:28:14 +0100	[thread overview]
Message-ID: <A6777035-DD19-48A0-A352-7D80C28D43EF@thornhill.no> (raw)
In-Reply-To: <838rjwrhce.fsf@gnu.org>



On 27 November 2022 08:23:29 CET, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Sun, 27 Nov 2022 08:11:00 +0100
>> From: Theodor Thornhill <theo@thornhill.no>
>> CC: 59252-done@debbugs.gnu.org,
>>  João Távora <joaotavora@gmail.com>
>> 
>> >Please remember to add the bug number, like this:
>> >
>> >* lisp/progmodes/eglot.el (eglot-server-programs): Add js-ts-mode as
>> >an alternative.  (Bug#59252)
>> >
>> >(I did that for you before pushing.)
>> 
>> Thanks - I can start creating the bug before the patch, so that I know what the bug number will be. It just often take a really long time before I get the acknowledge for the bug :)
>
>If you send only a single message to the bug tracker, and include the patch
>there, you indeed don't know the number, and then the person who pushed the
>commit needs to add that.  This is okay.  There's no need to send the patch
>in two parts (although you can do this if you feel like it).
>
>But if you send an updated patch, and already know the bug number, please
>add it.
>
>Thanks.

Thanks, I forgot I sent an updated patch on this issue, as I sent several patches yesterday!

Will do that in the future :)
Theo





      reply	other threads:[~2022-11-27  7:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-13 20:56 bug#59252: 29.0.50; Add new ts-modes to eglot-server-programs Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-14  3:25 ` Eli Zaretskii
2022-11-14  6:21   ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-14 13:10     ` Eli Zaretskii
2022-11-14 14:28       ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-26 20:15         ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-27  7:04           ` Stefan Kangas
2022-11-27  7:11             ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-27  7:23               ` Eli Zaretskii
2022-11-27  7:28                 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors [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=A6777035-DD19-48A0-A352-7D80C28D43EF@thornhill.no \
    --to=bug-gnu-emacs@gnu.org \
    --cc=59252-done@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=stefankangas@gmail.com \
    --cc=theo@thornhill.no \
    /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.