linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Sam James <sam@gentoo.org>
Cc: carlos@maiolino.me, linux-xfs@vger.kernel.org
Subject: Re: [ANNOUNCE] xfsprogs: for-next updated to 3ec53d438
Date: Fri, 2 Feb 2024 08:44:10 -0800	[thread overview]
Message-ID: <20240202164410.GJ616564@frogsfrogsfrogs> (raw)
In-Reply-To: <875xz7cqg9.fsf@gentoo.org>

On Fri, Feb 02, 2024 at 06:47:26AM +0000, Sam James wrote:
> 
> Sam James <sam@gentoo.org> writes:
> 
> > Sam James <sam@gentoo.org> writes:
> >
> >> I think
> >> https://lore.kernel.org/linux-xfs/20240122072351.3036242-1-sam@gentoo.org/
> >> is ready.
> >>
> >> See Christoph's comment wrt application order:
> >> https://lore.kernel.org/linux-xfs/Za4Yso9cEs+TzU8w@infradead.org/.
> >>
> >
> > Ping - I think it missed another push too. Please let me know if I
> > need to be doing something different.
> 
> (Oh wait, maybe the other one was a non-progs push.)

Huh?  The off64_t -> off_t conversion and the TIME_BITS=64 changes are
both xfsprogs.  Carlos hasn't merged either of those into for-next.  I'm
not sure if he's just going to release 6.6 as-is and move on to 6.7, or
what.

--D

> >
> >> thanks,
> >> sam
> 
> 

  reply	other threads:[~2024-02-02 16:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23 10:53 [ANNOUNCE] xfsprogs: for-next updated to 3ec53d438 Carlos Maiolino
2024-01-24 10:13 ` Sam James
2024-02-02  6:42   ` Sam James
2024-02-02  6:47     ` Sam James
2024-02-02 16:44       ` Darrick J. Wong [this message]
2024-02-05 23:24         ` Sam James
2024-02-07 13:56           ` Carlos Maiolino
2024-02-08  6:26             ` Sam James

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=20240202164410.GJ616564@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=carlos@maiolino.me \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sam@gentoo.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).