Hi Helge, On Thu, 09 May 2013 22:31:04 +0200 Helge Deller <deller@xxxxxx> wrote: > > On 05/08/2013 03:37 AM, Stephen Rothwell wrote: > > On Wed, 8 May 2013 00:11:02 +0200 Helge Deller <deller@xxxxxx> wrote: > >> > >> please pull the parisc architecture updates for v3.10 from: > >> > >> git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git parisc-for-3.10 > > > > Does this mean that the parisc tree I have in linux-next > > (git://git.kernel.org/pub/scm/linux/kernel/git/jejb/parisc-2.6.git#for-next) > > is defunct? > > Not sure. It will be either James or me who will send pull requests... > Of course we will agree who of us will do that and from which tree. > > So, would it hurt if you add a second parisc tree for linux-next? > I've just created a "for-next" branch in my git repository: > git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git#for-next I have no problem having both trees in linux-next (as long as you don't tread on each other's toes and cause merge problem too often :-)). I have added your tree from today (noting that it is empty). I have set you and the parisc mailing list as contacts. 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@xxxxxxxxxxxxxxxx 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:
pgptFzVqfdmpk.pgp
Description: PGP signature