From: hills <hills@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Document a reasonable practice for deleting mails
Date: Thu, 30 Mar 2023 16:26:03 +0200 [thread overview]
Message-ID: <20230330142603.l5EvgOBmDb5eLScrFrf0eAv_vAZqb4Mui8d1Wx09d44@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-237@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 393 bytes --]
New comment by hills on mblaze repository
https://github.com/leahneukirchen/mblaze/pull/237#issuecomment-1490403108
Comment:
> `-` missing before 365d.
Doh, sorry. I accidentally deleted it wrangling the escaping of the double quotes. I've replaced the patch.
Now might be a good time to ask why the double quotes are necessary? The nesting of quotes makes things a little untidy.
next prev parent reply other threads:[~2023-03-30 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 14:11 [PR PATCH] " hills
2023-03-30 14:20 ` leahneukirchen
2023-03-30 14:23 ` [PR PATCH] [Updated] " hills
2023-03-30 14:26 ` hills [this message]
2023-03-30 14:36 ` leahneukirchen
2023-03-30 14:36 ` [PR PATCH] [Merged]: " leahneukirchen
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=20230330142603.l5EvgOBmDb5eLScrFrf0eAv_vAZqb4Mui8d1Wx09d44@z \
--to=hills@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).