From: pr-tracker-bot@kernel.org
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: gfs2@lists.linux.dev, linux-kernel@vger.kernel.org,
cluster-devel@redhat.com,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [Cluster-devel] [GIT PULL] gfs2 fixes
Date: Tue, 05 Sep 2023 20:14:01 +0000 [thread overview]
Message-ID: <169394484194.28658.6576619504433985005.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <20230905161246.2042842-1-agruenba@redhat.com>
The pull request you sent on Tue, 5 Sep 2023 18:12:46 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-v6.5-rc5-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/65d6e954e37872fd9afb5ef3fc0481bb3c2f20f4
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
next prev parent reply other threads:[~2023-09-05 20:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 16:12 [Cluster-devel] [GIT PULL] gfs2 fixes Andreas Gruenbacher
2023-09-05 20:14 ` pr-tracker-bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-08 12:53 Andreas Gruenbacher
2023-08-08 17:00 ` pr-tracker-bot
2023-07-04 12:51 Andreas Gruenbacher
2023-07-04 18:59 ` pr-tracker-bot
2023-02-22 12:01 Andreas Gruenbacher
2023-02-22 22:27 ` pr-tracker-bot
2022-12-16 14:33 Andreas Gruenbacher
2022-12-17 14:28 ` pr-tracker-bot
2022-10-09 10:45 Andreas Gruenbacher
2022-10-11 3:43 ` pr-tracker-bot
2022-08-05 20:12 Andreas Gruenbacher
2022-08-06 22:08 ` pr-tracker-bot
2022-05-24 19:41 Andreas Gruenbacher
2022-05-25 2:16 ` pr-tracker-bot
2022-05-13 21:07 Andreas Gruenbacher
2022-05-13 21:35 ` Linus Torvalds
2022-05-13 21:38 ` pr-tracker-bot
2022-02-11 17:05 Andreas Gruenbacher
2022-02-11 19:47 ` Linus Torvalds
2022-02-11 21:40 ` Andreas Gruenbacher
2022-02-11 20:05 ` 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=169394484194.28658.6576619504433985005.pr-tracker-bot@kernel.org \
--to=pr-tracker-bot@kernel.org \
--cc=agruenba@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=gfs2@lists.linux.dev \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).