Stephen Rothwell <[email protected]> writes: > You just need to send me a git URL for your tree/branch (not a cgit or > gitweb URL, please), plus some idea of what the tree include and how it > is sent to Linus (directly or via another tree). The branch should > have a generic name (i.e. not including a version) as I will continuet > to fetch that branch every day until you tell me to stop. When your > code is ready to be included in linux-next, all you have to do is > update that branch to include the new code.
Hi Stephen, Thanks for the information. 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. Thank you, -- Gabriel Krisman Bertazi _______________________________________________ Linux-f2fs-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
