From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Carlos Maiolino <cem@kernel.org>,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: xfs: new code for 6.14 (needs [GIT PULL]?)
Date: Thu, 23 Jan 2025 13:22:55 -0800 [thread overview]
Message-ID: <20250123212255.GG1611770@frogsfrogsfrogs> (raw)
In-Reply-To: <CAHk-=whUe3wH4J1YGrdokVEgtb2hjteOdBttF=6ffHSYzakcBQ@mail.gmail.com>
On Thu, Jan 23, 2025 at 12:46:47PM -0800, Linus Torvalds wrote:
> On Thu, 23 Jan 2025 at 10:38, Darrick J. Wong <djwong@kernel.org> wrote:
> >
> > It's been a couple of days and this PR hasn't been merged yet. Is there
> > a reason to delay the merge, or is it simply that the mail was missing
> > the usual "[GIT PULL]" tag in the subject line and it didn't get
> > noticed?
>
> No, it's in my queue. You don't need to have the "git pull" in the
> subject, as long as it says "git" and "pull" _somewhere_, and the xfs
> pull request email does say that.
>
> But I tend to batch up merge window requests by area, and I did my
> initial filesystem pulls on Monday. The xfs pull hadn't come in at
> that point, and then I went on to different areas.
>
> I'm getting back to filesystems today, but since I have great
> time-planning abilities (not!) I also am on the road today at an
> Intel/AMD architecture meeting, so my pulls today are going to be a
> bit sporadic.
Ah, ok. Thanks for pulling! :)
--D
>
> Linus
>
prev parent reply other threads:[~2025-01-23 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 13:09 xfs: new code for 6.14 Carlos Maiolino
2025-01-23 18:38 ` xfs: new code for 6.14 (needs [GIT PULL]?) Darrick J. Wong
2025-01-23 20:46 ` Linus Torvalds
2025-01-23 21:09 ` Linus Torvalds
2025-01-23 21:22 ` Darrick J. Wong [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=20250123212255.GG1611770@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@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