From: pr-tracker-bot@kernel.org
To: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Cc: torvalds@linux-foundation.org, ntfs3@lists.linux.dev,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] ntfs3: bugfixes for 5.19
Date: Sat, 04 Jun 2022 00:06:00 +0000 [thread overview]
Message-ID: <165430116055.8653.4989553009324938778.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <c5c16f3d-c8a7-96b0-4fd6-056c4159fcef@paragon-software.com>
The pull request you sent on Fri, 3 Jun 2022 14:26:57 +0300:
> https://github.com/Paragon-Software-Group/linux-ntfs3.git ntfs3_for_5.19
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1f952675835bfe18d6ae494a5581724d68c52352
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
prev parent reply other threads:[~2022-06-04 0:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 11:26 [GIT PULL] ntfs3: bugfixes for 5.19 Konstantin Komarov
2022-06-04 0:06 ` pr-tracker-bot [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=165430116055.8653.4989553009324938778.pr-tracker-bot@kernel.org \
--to=pr-tracker-bot@kernel.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).