From: David Sterba <dave@jikos.cz>
To: dsterba@suse.cz, torvalds@linux-foundation.org,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Btrfs fixes for 5.18-rc3
Date: Thu, 14 Apr 2022 16:37:29 +0200 [thread overview]
Message-ID: <20220414143729.GP3658@twin.jikos.cz> (raw)
In-Reply-To: <cover.1649705056.git.dsterba@suse.com>
Hi,
I'm sending this from a different mail address after 2 days of no reply
and no merge of the btrfs updates (message body deleted in case it
triggers the spam filter). The mail is in lore archives at
https://lore.kernel.org/all/cover.1649705056.git.dsterba@suse.com/
next prev parent reply other threads:[~2022-04-14 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 21:31 [GIT PULL] Btrfs fixes for 5.18-rc3 David Sterba
2022-04-13 11:52 ` David Sterba
2022-04-14 14:37 ` David Sterba [this message]
2022-04-14 17:50 ` Linus Torvalds
2022-04-14 18:59 ` pr-tracker-bot
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=20220414143729.GP3658@twin.jikos.cz \
--to=dave@jikos.cz \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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