Skip to contentSkip to conversation

aio-next

DISCUSSION Benjamin LaHaise 2 participants 2 messages Jul 16, 2013 VFS

lore
Share & tools
lore
#0 lore raw

Hell Stephen,

There are shaping up to be a bunch of aio changes for the 3.12 tree, so I think it's time to start staging them in a git tree. Would you be willing to add my aio-next tree to linux-next so these patches can get a bit more exposure? The tree is at git://git.kvack.org/~bcrl/aio-next.git . Regards,

-ben

Signature · 7 lines
"Thought is the essence of where you are now."

--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to [email protected].  For more info on Linux AIO,
see: http://www.kvack.org/aio/
Don't email: <a href=mailto:"[email protected]">[email protected]</a>
#1 lore raw

Hi Ben,

Quoted 2 lines · On Tue, 16 Jul 2013 09:40:28 -0400 Benjamin LaHaise <[email protected]> wrote:

Hell Stephen,

Its not that bad :-)

Quoted 4 lines

There are shaping up to be a bunch of aio changes for the 3.12 tree, so I think it's time to start staging them in a git tree. Would you be willing to add my aio-next tree to linux-next so these patches can get a bit more exposure? The tree is at git://git.kvack.org/~bcrl/aio-next.git . Regards,

Added from today with just you as the contact in case of conflicts, build problems etc.

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.

Signature · 15 lines
Cheers,
Stephen Rothwell 
[email protected]

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.