From: Philip Kaludercic <philipk@posteo.net>
To: Niall Dooley <dooleyn@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Don't see PATCH on bug-gnu-emacs
Date: Fri, 24 Nov 2023 20:57:30 +0000 [thread overview]
Message-ID: <8734wu3m4l.fsf@posteo.net> (raw)
In-Reply-To: <CADS3Lq7j5jAaYa2pqvY2uR4p=Obemqgp39S5a_jOAdoyn1Ak2g@mail.gmail.com> (Niall Dooley's message of "Fri, 24 Nov 2023 19:39:10 +0100")
Niall Dooley <dooleyn@gmail.com> writes:
> 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? Should I send the mail
> again with the attachment or reply to my original mail?
Both should appear on the mailing list, the issue with inline patches
depending on your MUA is that that might be misrendered. I couldn't
find anything by your name on bug-gnu-emacs@gnu.org, so I guess
something else went wrong. Try resending your message -- even if you
make a mistake, it is nothing to worry about, it happens all the time
and nobody will get annoyed or anything like that.
> Thanks for your time.
next prev parent reply other threads:[~2023-11-24 20:57 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 [this message]
2023-11-25 7:02 ` Eli Zaretskii
2023-11-25 10:07 ` Michael Albinus
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=8734wu3m4l.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=dooleyn@gmail.com \
--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).