From: Nick Dokos <ndokos@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] org-lint: Fix invocation with C-u prefix argument
Date: Wed, 8 Jun 2022 23:10:08 -0400 [thread overview]
Message-ID: <3b6ce84d-085d-2acc-fa44-738ac5f668b5@gmail.com> (raw)
In-Reply-To: <87tu8vqo46.fsf@localhost>
On 6/8/22 09:30, Ihor Radchenko wrote:
> Nick Dokos <ndokos@gmail.com> writes:
>
>>> LGTM! Is there any reason you did not push the patch upstream yourself?
>>>
>> ISTR I used to have push access to the repo, but in some repo move I
>> think I've lost it and I've never arranged to get it back. At least, I
>> *think* that was the case - but perhaps given my general state of
>> discombobulation, you don't want me to be committing things to the
>> repo in any case :-) Better to have some eyes on patches first...
> Ok. AFAIK, after we moved the repo to savannah, you may need to create
> an account at https://savannah.gnu.org/ and request access from Bastien.
>
> Note that you don't have to commit without having extra pairs of eyes
> on the patches. You can post the patch here, get comments, and then
> apply the patch yourself if everything is ok. (Yes, I am lazy to apply
> patches from others if I don't have to).
>
> Applied onto main via 9fd5349d0.
> I did not apply onto bugfix because Bastien asked not to apply
> non-critical fixed until Emacs 28.2 is out.
>
> Best,
> Ihor
Thank you! I will try to get commit rights again before posting another
patch. I appreciate your patience and help (and the enormous
contribution you have made to Org mode too!)
--
Nick
prev parent reply other threads:[~2022-06-09 3:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 20:08 [PATCH] org-lint: Fix invocation with C-u prefix argument Nick Dokos
2022-06-02 5:09 ` Ihor Radchenko
2022-06-06 14:39 ` Nick Dokos
2022-06-08 13:30 ` Ihor Radchenko
2022-06-09 3:10 ` Nick Dokos [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=3b6ce84d-085d-2acc-fa44-738ac5f668b5@gmail.com \
--to=ndokos@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@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 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).