From: David Sterba <dsterba@suse.cz>
To: Mark Harmstone <mark@harmstone.com>
Cc: linux-btrfs@vger.kernel.org, wqu@suse.com
Subject: Re: [PATCH] btrfs: fix error messages in btrfs_check_features()
Date: Mon, 23 Feb 2026 19:59:00 +0100 [thread overview]
Message-ID: <20260223185900.GO26902@twin.jikos.cz> (raw)
In-Reply-To: <20260218111346.31243-1-mark@harmstone.com>
On Wed, Feb 18, 2026 at 11:13:40AM +0000, Mark Harmstone wrote:
> Commit d7f67ac9
Also please configure your git so the hashes are at least 12 characters,
I've been using 14 and I think others do too. This is 'core.abbrev'
config.
prev parent reply other threads:[~2026-02-23 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 11:13 [PATCH] btrfs: fix error messages in btrfs_check_features() Mark Harmstone
2026-02-18 20:37 ` Qu Wenruo
2026-02-23 18:55 ` David Sterba
2026-02-23 18:59 ` David Sterba [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260223185900.GO26902@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=mark@harmstone.com \
--cc=wqu@suse.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox