Hi,
Please add a tree to linux-next. It contains some cleanup for Sharp
Zaurus PDA's. Since it contains a number of patches, it's preferable
to test it via linux-next, before commiting to Russell's/ALSA tree.
The url to pull is git://github.com/lumag/linux-2.6.git#for-next
Thank you.
--
With best wishes
Dmitry
Hi Dmitry,
On Wed, 13 Aug 2008 20:16:55 +0400 Dmitry Baryshkov <[email protected]> wrote:
>
> Please add a tree to linux-next. It contains some cleanup for Sharp
> Zaurus PDA's. Since it contains a number of patches, it's preferable
> to test it via linux-next, before commiting to Russell's/ALSA tree.
I assume you have already posted these changes somewhere and had them
reviewed and unit tested them, right?
> The url to pull is git://github.com/lumag/linux-2.6.git#for-next
$ git ls-remote git://github.com/lumag/linux-2.6.git
fatal: protocol error: expected sha/ref, got '
*********'
Permission denied. Repository is not public.
*********'
--
Cheers,
Stephen Rothwell [email protected]
http://www.canb.auug.org.au/~sfr/
2008/8/14 Stephen Rothwell <[email protected]>:
> Hi Dmitry,
>
> On Wed, 13 Aug 2008 20:16:55 +0400 Dmitry Baryshkov <[email protected]> wrote:
>>
>> Please add a tree to linux-next. It contains some cleanup for Sharp
>> Zaurus PDA's. Since it contains a number of patches, it's preferable
>> to test it via linux-next, before commiting to Russell's/ALSA tree.
>
> I assume you have already posted these changes somewhere and had them
> reviewed and unit tested them, right?
>
>> The url to pull is git://github.com/lumag/linux-2.6.git#for-next
>
> $ git ls-remote git://github.com/lumag/linux-2.6.git
> fatal: protocol error: expected sha/ref, got '
> *********'
>
> Permission denied. Repository is not public.
>
> *********'
That's the github problem. I'll try to find another place to host this
git and will send a request again.
Sorry for the noise.
--
With best wishes
Dmitry
Hi Kees,
On Mon, 22 Oct 2012 08:44:26 -0700 Kees Cook <[email protected]> wrote:
>
> Now that we're past rc1, can you please add my tree to your linux-next pulls?
>
> drop-experimental git
> git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git#linux-next
Thanks for the reminder. It will be included 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
[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.