From: Ihor Radchenko <yantar92@gmail.com>
To: Alan Ristow <alan@ristow.info>
Cc: Carlo Tambuatco <oraclmaster@gmail.com>,
Org-Mode Mailing List <emacs-orgmode@gnu.org>,
Gustavo Barros <gusbrs.2016@gmail.com>,
Bhavin Gandhi <bhavin7392@gmail.com>
Subject: Re: [PATCH] Bug: Duplicate logbook entry for repeated tasks [9.4.6 (9.4.6-gab9f2a @ /home/gustavo/.emacs.d/elpa/org-9.4.6/)]
Date: Sat, 17 Jul 2021 21:51:08 +0800 [thread overview]
Message-ID: <87im196oc3.fsf@localhost> (raw)
In-Reply-To: <907e39a9-75fa-a99f-7237-a754a8d795f7@ristow.info>
Alan Ristow <alan@ristow.info> writes:
> Finally, as a newbie here myself, I have a naïve question of my own:
> Provided the patch proves successful, how/when is it applied to the
> official org repo? Is it up to Ihor (or somebody else) to make a pull
> request, for example?
An email with [PATCH] in header is the pull request for Org :) You can
see a list of patches, confirmed bugs, and help requests in
https://updates.orgmode.org/
The emails replying to the patch email are the comments to the pull
request.
The merge is up to Org maintainers. They patches are reviewed and merged
as the maintainers get some free time to do it.
Best,
Ihor
next prev parent reply other threads:[~2021-07-17 13:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 13:39 Bug: Duplicate logbook entry for repeated tasks [9.4.6 (9.4.6-gab9f2a @ /home/gustavo/.emacs.d/elpa/org-9.4.6/)] Gustavo Barros
2021-06-14 18:01 ` Bhavin Gandhi
2021-06-14 18:41 ` Gustavo Barros
2021-07-10 13:48 ` [PATCH] " Ihor Radchenko
2021-07-10 16:46 ` Gustavo Barros
2021-07-10 17:14 ` Bhavin Gandhi
2021-07-11 1:29 ` Ihor Radchenko
2021-07-11 5:40 ` Ihor Radchenko
2021-07-11 5:57 ` Ihor Radchenko
2021-07-12 17:50 ` Bhavin Gandhi
2021-07-13 2:55 ` [PATCH] " Carlo Tambuatco
2021-07-13 15:35 ` Alan Ristow
2021-07-13 18:08 ` Bhavin Gandhi
2021-07-17 13:51 ` Ihor Radchenko [this message]
2021-07-17 13:41 ` [PATCH] " Ihor Radchenko
2021-09-25 15:25 ` Bastien
2021-09-25 18:15 ` Gustavo Barros
2021-09-26 6:26 ` Bastien
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=87im196oc3.fsf@localhost \
--to=yantar92@gmail.com \
--cc=alan@ristow.info \
--cc=bhavin7392@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=gusbrs.2016@gmail.com \
--cc=oraclmaster@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.