From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mless N:x seems off-by-one.
Date: Sat, 13 Jul 2024 15:59:07 +0200 [thread overview]
Message-ID: <20240713135907.88C3D2A3AC@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-261@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 210 bytes --]
New comment by leahneukirchen on mblaze repository
https://github.com/leahneukirchen/mblaze/issues/261#issuecomment-2226916493
Comment:
I think that's not avoidable, as the first file is the scan overview...
next prev parent reply other threads:[~2024-07-13 13:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 0:41 [ISSUE] " rnkn
2024-07-12 19:13 ` leahneukirchen
2024-07-13 2:48 ` rnkn
2024-07-13 2:50 ` rnkn
2024-07-13 13:59 ` leahneukirchen [this message]
2024-07-14 8:33 ` rnkn
2024-07-14 8:39 ` rnkn
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=20240713135907.88C3D2A3AC@inbox.vuxu.org \
--to=leahneukirchen@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).