From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: dsterba@suse.cz
Cc: Srivathsa Dara <srivathsa.d.dara@oracle.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
Rajesh Sivaramasubramaniom
<rajesh.sivaramasubramaniom@oracle.com>,
Junxiao Bi <junxiao.bi@oracle.com>, "clm@fb.com" <clm@fb.com>,
"josef@toxicpanda.com" <josef@toxicpanda.com>,
"dsterba@suse.com" <dsterba@suse.com>
Subject: Re: [PATCH v2] btrfs-progs: convert: Add 64 bit block numbers support
Date: Thu, 13 Jun 2024 09:55:56 +0930 [thread overview]
Message-ID: <2d1a8153-274b-481e-bb0a-63504d1cbe01@gmx.com> (raw)
In-Reply-To: <20240613002301.GT18508@twin.jikos.cz>
在 2024/6/13 09:53, David Sterba 写道:
[...]
>>
>> Any good idea to go forward?
>> Update CI (which seems impossible) or make the mke2fs part as mayfail
>> and skip it?
>
> I think using mayfail for mke2fs is the best option, I don't want to
> check versions. The release of 1.46.5 is 2021-12-30, this is not that
> old and likely widely used. Skipping the particular case is not a big
> deal as it'll be covered on other testing instances.
Sounds good to me.
Just add an extra comment on the situation.
Although I really hope github CI can someday updates its infrastructures.
Thanks,
Qu
next prev parent reply other threads:[~2024-06-13 0:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 10:22 [PATCH v2] btrfs-progs: convert: Add 64 bit block numbers support Srivathsa Dara
2024-06-06 22:28 ` Qu Wenruo
2024-06-11 6:03 ` Srivathsa Dara
2024-06-12 20:37 ` David Sterba
2024-06-13 0:02 ` David Sterba
2024-06-13 0:10 ` Qu Wenruo
2024-06-13 0:23 ` David Sterba
2024-06-13 0:25 ` Qu Wenruo [this message]
2024-06-13 0:52 ` David Sterba
2024-06-13 1:23 ` David Sterba
2024-06-13 18:27 ` [External] : " Srivathsa Dara
2024-06-13 18:32 ` Srivathsa Dara
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=2d1a8153-274b-481e-bb0a-63504d1cbe01@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=josef@toxicpanda.com \
--cc=junxiao.bi@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rajesh.sivaramasubramaniom@oracle.com \
--cc=srivathsa.d.dara@oracle.com \
/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