From: Max Nikulin <firstname.lastname@example.org>
To: Robert Goldman <email@example.com>
Subject: Re: [PATCH v3] Fix FAQ entry about mailto links.
Date: Fri, 25 Feb 2022 19:20:31 +0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 16/02/2022 08:29, Robert Goldman wrote:
> On 14 Feb 2022, at 7:22, Max Nikulin wrote:
>> On 11/02/2022 00:42, Robert Goldman wrote:
>> I am sending the updated patch and a diff to your edits to highlight
>> my latest changes.
> Some responses below, then I think merging would be fine. I am losing my
> ability and energy to process these patch files, honestly.
One patch was for clean master HEAD state, another file was diff in
comparison to your variant. The latter could be applied on the top of
your patches or one could just read it to see changes.
> To be honest, I'm not sure what value this whole comment section has.
> Given that, I'm ok with whatever you want to do: leave it as it, try to
> fix it, or just remove it altogether. I actually think that removing it
> might be best. It's confusing, and will eventually become out-of-date,
> and who will update it?
I pushed the patch without comment block. I decided to suggest
`org-link-set-parameters' instead of customization of
`org-link-parameters'. See updated variant at
Robert, thank you for suggesting corrections and for reviewing my patches.
P.S. I was surprised that Apple does not provide online version of man
pages for MacOS utilities.
next prev parent reply other threads:[~2022-02-25 13:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 18:34 [PATCH] Fix FAQ entry about mailto links Robert Goldman
2022-01-07 11:03 ` Max Nikulin
2022-02-07 16:59 ` Max Nikulin
2022-02-10 17:42 ` Robert Goldman
2022-02-14 13:22 ` [PATCH v3] " Max Nikulin
2022-02-16 1:29 ` Robert Goldman
2022-02-25 12:20 ` Max Nikulin [this message]
2022-03-12 14:35 ` Max Nikulin
2022-03-12 15:50 ` [PATCH] " Max Nikulin
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).