From: dalanicolai <dalanicolai@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to send patch for org-contrib?
Date: Thu, 25 May 2023 22:45:45 +0200 [thread overview]
Message-ID: <CACJP=3munhMHV+W7Y=FQgWvXy6Mh2RGhq6eLz2dZrThYkzRkBw@mail.gmail.com> (raw)
In-Reply-To: <87ttw0wu78.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]
Ah great, good to know... thanks again!
On Thu, 25 May 2023 at 12:57, Ihor Radchenko <yantar92@posteo.net> wrote:
> dalanicolai <dalanicolai@gmail.com> writes:
>
> > I have just created a patch for org-eldoc.el in org-contrib.
> > I tried to send it using the 'Prepare a patchset' functionality on
> > sourcehut which
> > requires me to enter some email-address for where to send it to.
> > As I have no idea where to send it, I simply filled in the address of
> this
> > mailing list.
> > However, I do not see the message appear in my inbox.
> >
> > So, I am wondering, how should I send a patch for org-contrib?
>
> You patch did reach the Org ML:
>
> https://list.orgmode.org/168500905821.7612.7160946900807283240-0@git.sr.ht/T/#t
>
> It is also likely listed somewhere in your sr.ht account, like in
> activity feed (mine is https://sr.ht/~yantar92/). In future, you can add
> your personal email to CC when sending a patchset.
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at <https://orgmode.org/>.
> Support Org development at <https://liberapay.com/org-mode>,
> or support my work at <https://liberapay.com/yantar92>
>
[-- Attachment #2: Type: text/html, Size: 2131 bytes --]
prev parent reply other threads:[~2023-05-25 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 10:12 How to send patch for org-contrib? dalanicolai
2023-05-25 11:01 ` Ihor Radchenko
2023-05-25 20:45 ` dalanicolai [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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACJP=3munhMHV+W7Y=FQgWvXy6Mh2RGhq6eLz2dZrThYkzRkBw@mail.gmail.com' \
--to=dalanicolai@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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/org-mode.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).