[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20211028204706.7c3aee30@canb.auug.org.au>
Date: Thu, 28 Oct 2021 20:47:06 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Gabriel Krisman Bertazi <krisman@...labora.com>
Cc: Christoph Hellwig <hch@....de>,
Shreeya Patel <shreeya.patel@...labora.com>,
linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net
Subject: Re: Track unicode tree in linux-next (was Re: [PATCH 10/11]
unicode: Add utf8-data module)
Hi Gabriel,
On Wed, 27 Oct 2021 23:00:55 -0300 Gabriel Krisman Bertazi <krisman@...labora.com> wrote:
>>
> I'd like to ask you to track the branch 'for-next' of the following repository:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/krisman/unicode.git
>
> This branch is used as a staging area for development of the Unicode
> subsystem used by native case-insensitive filesystems for file name
> normalization and casefolding. It goes to Linus through Ted Ts'o's ext4
> tree.
Added from today.
Thanks for adding your subsystem tree as a participant of linux-next. As
you may know, this is not a judgement of your code. The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have
been:
* submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary.
--
Cheers,
Stephen Rothwell
sfr@...b.auug.org.au
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists