From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Niall Dooley <dooleyn@gmail.com>, emacs-devel@gnu.org
Subject: Re: Don't see PATCH on bug-gnu-emacs
Date: Sat, 25 Nov 2023 11:07:07 +0100 [thread overview]
Message-ID: <87v89qywms.fsf@gmx.de> (raw)
In-Reply-To: <83plzye2nt.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 25 Nov 2023 09:02:30 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
Hi,
>> I submitted a simple patch email titled as follows over two hours ago.
>>
>> [PATCH] eglot: Add ruff-lsp as an alternative python server
>>
>> This is my first patch so likely I did something wrong.
>>
>> I did not attach a patch file but rather sent it inline in the mail.
>> Reading CONTRIBUTE more carefully I now see an attachment is preferred.
>> Is this why it does not appear on the list?
>
> No, inline patches are also okay, although attachments are preferable.
>
>> Should I send the mail again with the attachment or reply to my
>> original mail?
>
> Please wait for Michael (CC'ed) to chime in and tell why your
> submission didn't get through.
In the mailman logs, there are the respective entries:
--8<---------------cut here---------------start------------->8---
Nov 24 10:53:35 2023 (731) Debbugs-submit post from dooleyn@gmail.com held, message-id=<20231124155236.49559-1-dooleyn@gmail.com>: Post by non-member to a members-only list
Nov 24 17:43:21 2023 (731) Debbugs-submit post from dooleyn@gmail.com held, message-id=<CADS3Lq4sAqT4vVyBm73A4B-U0erdmMCEY+voftkDRorxxNZwZg@mail.gmail.com>: Post by non-member to a members-only list
Nov 25 03:17:32 2023 (29192) debbugs-submit: held message approved, message-id: <20231124155236.49559-1-dooleyn@gmail.com>
Nov 25 03:17:32 2023 (29192) debbugs-submit: held message approved, message-id: <CADS3Lq4sAqT4vVyBm73A4B-U0erdmMCEY+voftkDRorxxNZwZg@mail.gmail.com>
--8<---------------cut here---------------end--------------->8---
And indeed, <20231124155236.49559-1-dooleyn@gmail.com> and
<CADS3Lq4sAqT4vVyBm73A4B-U0erdmMCEY+voftkDRorxxNZwZg@mail.gmail.com> are
visible in ML <bug-gnu-emacs.gnu.org>. So everything is fine.
There was a longer delay than usual before approving, but this could
happen if none of the moderators is online. But it is still less than a
day...
Best regards, Michael.
next prev parent reply other threads:[~2023-11-25 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 18:39 Don't see PATCH on bug-gnu-emacs Niall Dooley
2023-11-24 20:57 ` Philip Kaludercic
2023-11-25 7:02 ` Eli Zaretskii
2023-11-25 10:07 ` Michael Albinus [this message]
2023-11-25 11:02 ` Niall Dooley
2023-11-25 10:34 ` Niall Dooley
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=87v89qywms.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=dooleyn@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).