From: Stephen Rothwell <sfr@canb.auug.org.au> To: "\"Jörn Engel\"" <joern@logfs.org> Cc: Arnd Bergmann <arnd@arndb.de>, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-mtd@lists.infradead.org Subject: Re: [PATCH 0/17] [LogFS] New flash filesystem Date: Fri, 27 Nov 2009 15:24:59 +1100 [thread overview] Message-ID: <20091127152459.b427f4e5.sfr@canb.auug.org.au> (raw) In-Reply-To: <20091126083614.GI10944@logfs.org> [-- Attachment #1: Type: text/plain, Size: 2083 bytes --] Hi Jörn, On Thu, 26 Nov 2009 09:36:15 +0100 Jörn Engel <joern@logfs.org> wrote: > > Being of sound state of mind, I hereby request that you add :-) > git://git.kernel.org/pub/scm/linux/kernel/git/joern/logfs.git > to linux-next. > > Something like that? Or would you doubt my state of mind if I willing > accept the risk of breaking others' compile and suffering the angry > emails that inevitably follow? Sometimes I question my own state of mind :-) I have added the master branch of the above tree from today. Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgment 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@canb.auug.org.au Legal Stuff: By participating in linux-next, your subsystem tree contributions are public and will be included in the linux-next trees. You may be sent e-mail messages indicating errors or other issues when the patches/commits from your subsystem tree are merged and tested in linux-next. These messages may also be cross-posted to the linux-next mailing list, the linux-kernel mailing list, etc. The linux-next tree project and IBM (my employer) make no warranties regarding the linux-next project, the testing procedures, the results, the e-mails, etc. If you don't agree to these ground rules, let me know and I'll remove your tree from participation in linux-next. [-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Rothwell <sfr@canb.auug.org.au> To: "\"Jörn Engel\"" <joern@logfs.org> Cc: linux-fsdevel@vger.kernel.org, linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de> Subject: Re: [PATCH 0/17] [LogFS] New flash filesystem Date: Fri, 27 Nov 2009 15:24:59 +1100 [thread overview] Message-ID: <20091127152459.b427f4e5.sfr@canb.auug.org.au> (raw) In-Reply-To: <20091126083614.GI10944@logfs.org> [-- Attachment #1: Type: text/plain, Size: 2083 bytes --] Hi Jörn, On Thu, 26 Nov 2009 09:36:15 +0100 Jörn Engel <joern@logfs.org> wrote: > > Being of sound state of mind, I hereby request that you add :-) > git://git.kernel.org/pub/scm/linux/kernel/git/joern/logfs.git > to linux-next. > > Something like that? Or would you doubt my state of mind if I willing > accept the risk of breaking others' compile and suffering the angry > emails that inevitably follow? Sometimes I question my own state of mind :-) I have added the master branch of the above tree from today. Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgment 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@canb.auug.org.au Legal Stuff: By participating in linux-next, your subsystem tree contributions are public and will be included in the linux-next trees. You may be sent e-mail messages indicating errors or other issues when the patches/commits from your subsystem tree are merged and tested in linux-next. These messages may also be cross-posted to the linux-next mailing list, the linux-kernel mailing list, etc. The linux-next tree project and IBM (my employer) make no warranties regarding the linux-next project, the testing procedures, the results, the e-mails, etc. If you don't agree to these ground rules, let me know and I'll remove your tree from participation in linux-next. [-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-11-27 4:25 UTC|newest] Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-11-20 19:37 [PATCH 0/17] [LogFS] New flash filesystem Joern Engel 2009-11-20 19:37 ` [PATCH 1/17] [LogFS] Documentation Joern Engel 2009-11-20 19:37 ` Joern Engel 2009-11-20 19:37 ` [PATCH 2/17] [LogFS] compr.c Joern Engel 2009-11-20 19:37 ` [PATCH 3/17] [LogFS] dev_bdev.c Joern Engel 2009-11-20 19:37 ` [PATCH 4/17] [LogFS] dev_mtd.c Joern Engel 2009-11-20 19:37 ` [PATCH 5/17] [LogFS] dir.c Joern Engel 2009-11-23 11:17 ` Dan Carpenter 2009-11-23 11:17 ` Dan Carpenter 2009-11-23 11:17 ` Dan Carpenter 2009-11-23 13:32 ` Jörn Engel 2009-11-23 13:32 ` Jörn Engel 2009-11-23 13:32 ` Jörn Engel 2009-11-20 19:37 ` [PATCH 6/17] [LogFS] file.c Joern Engel 2009-11-20 19:37 ` [PATCH 7/17] [LogFS] gc.c Joern Engel 2009-11-20 19:37 ` [PATCH 8/17] [LogFS] inode.c Joern Engel 2009-11-20 19:37 ` [PATCH 9/17] [LogFS] journal.c Joern Engel 2009-11-20 19:37 ` [PATCH 10/17] [LogFS] logfs.h Joern Engel 2009-11-20 19:38 ` [PATCH 11/17] [LogFS] logfs_abi.h Joern Engel 2009-11-20 19:38 ` [PATCH 12/17] [LogFS] readwrite.c Joern Engel 2009-11-23 12:33 ` Pekka Enberg 2009-11-23 12:33 ` Pekka Enberg 2009-11-23 12:33 ` Pekka Enberg 2009-11-23 13:15 ` Jörn Engel 2009-11-23 13:15 ` Jörn Engel 2009-11-20 19:38 ` [PATCH 13/17] [LogFS] segment.c Joern Engel 2009-11-20 19:38 ` [PATCH 14/17] [LogFS] super.c Joern Engel 2009-11-20 19:38 ` [PATCH 15/17] [LogFS] btree headers Joern Engel 2009-11-20 19:38 ` [PATCH 16/17] [LogFS] btree.c Joern Engel 2009-11-20 19:38 ` [PATCH 17/17] [LogFS] Kconfig and Makefile Joern Engel 2009-11-20 19:38 ` [PATCH 18/17] [LogFS] fio support Joern Engel 2009-11-23 12:18 ` [PATCH 0/17] [LogFS] New flash filesystem Arnd Bergmann 2009-11-23 12:18 ` Arnd Bergmann 2009-11-25 15:55 ` Jörn Engel 2009-11-25 15:55 ` Jörn Engel 2009-11-25 15:55 ` Jörn Engel 2009-11-25 23:51 ` Stephen Rothwell 2009-11-25 23:51 ` Stephen Rothwell 2009-11-26 8:36 ` Jörn Engel 2009-11-26 8:36 ` Jörn Engel 2009-11-26 8:36 ` Jörn Engel 2009-11-27 4:24 ` Stephen Rothwell [this message] 2009-11-27 4:24 ` Stephen Rothwell
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=20091127152459.b427f4e5.sfr@canb.auug.org.au \ --to=sfr@canb.auug.org.au \ --cc=arnd@arndb.de \ --cc=joern@logfs.org \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mtd@lists.infradead.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.