From: Carlos Maiolino <cem@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [ANNOUNCE] xfsprogs v6.7.0 released
Date: Wed, 17 Apr 2024 22:15:23 +0200 [thread overview]
Message-ID: <ftqfopwvmyponcod6miad2ammahmwddkfjel2wodwchfi32eeh@znsirj6nta3m> (raw)
In-Reply-To: <20240417153456.GZ11948@frogsfrogsfrogs>
On Wed, Apr 17, 2024 at 08:34:56AM -0700, Darrick J. Wong wrote:
> On Wed, Apr 17, 2024 at 05:32:15PM +0200, Carlos Maiolino wrote:
> > On Wed, Apr 17, 2024 at 08:18:34AM -0700, Darrick J. Wong wrote:
> > > On Wed, Apr 17, 2024 at 10:13:52AM +0200, Carlos Maiolino wrote:
> > > > Hi folks,
> > > >
> > > > The xfsprogs repository at:
> > > >
> > > > git://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git
> > > >
> > > > has just been updated.
> > > >
> > > > Patches often get missed, so if your outstanding patches are properly reviewed
> > > > on the list and not included in this update, please let me know.
> > >
> > > Ah well, I was hoping to get
> > > https://lore.kernel.org/linux-xfs/171142126291.2211955.14829143192552278353.stgit@frogsfrogsfrogs/
> > > and
> > > https://lore.kernel.org/linux-xfs/20240326192448.GI6414@frogsfrogsfrogs/
> > > in for 6.7.
> >
> > To be honest, one of the reasons I decided to release 6.7 today, was because these patches were
> > cooking for too long on the list, and I wanted to pull them this week, but not delay 6.7 because of
> > them as I want to also not delay 6.8 for too long, mostly libxfs-sync and what we already have on
> > the list. The debian one I totally missed it btw
> >
> > Also, I was assuming you were going to send PRs for these series according to our previous talks,
> > will you still submit PRs or shall I pull them from the list?
> >
> > I'll try to pull those patches you meant asap.
> >
> > I could do a 6.7.1 release with the debian patch if this is really required, but I don't think it
> > will change anything if I simply postpone it for 6.8.
>
> Well if we get a 6.8 release out fairly fast then it might not matter --
> Debian are busy rebuilding the world with 64-bit time_t and altered
> package names.
We are getting close to kernel 6.9 release, and I don't want to keep xfsprogs and I want to try to
keep xfsprogs just behind kernel, so, I do plan to release 6.8 on the following couple weeks.
Carlos
>
> --D
>
> >
> > >
> > > --D
> > >
> > > >
> > > > The for-next branch has also been updated to match the state of master.
> > > >
> > > > The new head of the master branch is commit:
> > > >
> > > > 09ba6420a1ee2ca4bfc763e498b4ee6be415b131
> > > >
> > > > --
> > > > Carlos
> > > >
> > >
> >
>
prev parent reply other threads:[~2024-04-17 20:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 8:13 [ANNOUNCE] xfsprogs v6.7.0 released Carlos Maiolino
2024-04-17 15:18 ` Darrick J. Wong
2024-04-17 15:19 ` Christoph Hellwig
2024-04-17 15:23 ` Darrick J. Wong
2024-04-17 15:38 ` Carlos Maiolino
2024-04-17 15:33 ` Carlos Maiolino
2024-04-17 15:32 ` Carlos Maiolino
2024-04-17 15:34 ` Darrick J. Wong
2024-04-17 20:15 ` Carlos Maiolino [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=ftqfopwvmyponcod6miad2ammahmwddkfjel2wodwchfi32eeh@znsirj6nta3m \
--to=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.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).