New GIT net tree naming...

New GIT net tree naming...

[David Miller]

Based upon feedback from Andrew and others I'm now starting
to use a new naming scheme for my GIT trees:

For changes against Linus's current tree:

   master.kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6.git

For development meant to be merged in the next merge
window we have:

   master.kernel.org:/pub/scm/linux/kernel/git/davem/net-next-2.6.git

Andrew/Stephen, let me know if this works for you.  This way
the tree names will never change.

Re: New GIT net tree naming...

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 872 bytes --]

Hi Dave,

On Sat, 19 Apr 2008 17:35:10 -0700 (PDT) David Miller <davem@davemloft.net> wrote:
>
> Based upon feedback from Andrew and others I'm now starting
> to use a new naming scheme for my GIT trees:
> 
> For changes against Linus's current tree:
> 
>    master.kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6.git

I have added this as net-current in the linux-next tree.  It will be
merged early after Linus' tree.

> For development meant to be merged in the next merge
> window we have:
> 
>    master.kernel.org:/pub/scm/linux/kernel/git/davem/net-next-2.6.git

And updated my URL for the net tree.

> Andrew/Stephen, let me know if this works for you.  This way
> the tree names will never change.

That is very nice, thanks.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: New GIT net tree naming...

[Ian Brown]

Hello
Sorry for my ignorance, but what is the password that I need to enter
when prompted to ?

when running:
git-clone master.kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6.git master
Initialized empty Git repository in /work/src/master/.git/
I get:
root@master.kernel.org's password:

The same is for the
master.kernel.org:/pub/scm/linux/kernel/git/davem/net-next-2.6.git
tree.

Regards,
Ian



On Sun, Apr 20, 2008 at 3:35 AM, David Miller <davem@davemloft.net> wrote:
>
>  Based upon feedback from Andrew and others I'm now starting
>  to use a new naming scheme for my GIT trees:
>
>  For changes against Linus's current tree:
>
>    master.kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6.git
>
>  For development meant to be merged in the next merge
>  window we have:
>
>    master.kernel.org:/pub/scm/linux/kernel/git/davem/net-next-2.6.git
>
>  Andrew/Stephen, let me know if this works for you.  This way
>  the tree names will never change.
>  --
>  To unsubscribe from this list: send the line "unsubscribe netdev" in
>  the body of a message to majordomo@vger.kernel.org
>  More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: New GIT net tree naming...

[David Miller]

From: "Ian Brown" <ianbrn@gmail.com>
Date: Mon, 21 Apr 2008 10:53:16 +0300

> Sorry for my ignorance, but what is the password that I need to enter
> when prompted to ?
> 
> when running:
> git-clone master.kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6.git master
> Initialized empty Git repository in /work/src/master/.git/
> I get:
> root@master.kernel.org's password:
> 
> The same is for the
> master.kernel.org:/pub/scm/linux/kernel/git/davem/net-next-2.6.git
> tree.

The URL I posted works for people who have kernel.org accounts.

Others, such as yourself, need to transform that URL into the
public form, for example:

	git://.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git

and:

	git://.kernel.org/pub/scm/linux/kernel/git/davem/net-next-2.6.git

Re: New GIT net tree naming...

[YOSHIFUJI Hideaki / 吉藤英明]

In article <d0383f90804210053w538c20dfp6495072632320abe@mail.gmail.com> (at Mon, 21 Apr 2008 10:53:16 +0300), "Ian Brown" <ianbrn@gmail.com> says:

> when running:
> git-clone master.kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6.git master
> Initialized empty Git repository in /work/src/master/.git/
> I get:
> root@master.kernel.org's password:
> 
> The same is for the
> master.kernel.org:/pub/scm/linux/kernel/git/davem/net-next-2.6.git
> tree.

git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next-2.6.git

I'd not recommend to run git as root, BTW.

--yoshfuji

Re: New GIT net tree naming...

[Ian Brown]

Thanks.

>  git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git
>  git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next-2.6.git

OK , these URL worked for me.

last question:

Do I understand correctly - patches sent for this mailing list from
now on are for davem/net-2.6.git tree and not for the
davem/net-next-2.6.git ? or they can be for both, and we can
understand from the patch title to which git tree they are ?
IB


On Mon, Apr 21, 2008 at 11:00 AM, YOSHIFUJI Hideaki / 吉藤英明
<yoshfuji@linux-ipv6.org> wrote:
> In article <d0383f90804210053w538c20dfp6495072632320abe@mail.gmail.com> (at Mon, 21 Apr 2008 10:53:16 +0300), "Ian Brown" <ianbrn@gmail.com> says:
>
>  > when running:
>  > git-clone master.kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6.git master
>  > Initialized empty Git repository in /work/src/master/.git/
>  > I get:
>  > root@master.kernel.org's password:
>  >
>  > The same is for the
>  > master.kernel.org:/pub/scm/linux/kernel/git/davem/net-next-2.6.git
>  > tree.
>
>  git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git
>  git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next-2.6.git
>
>  I'd not recommend to run git as root, BTW.
>
>  --yoshfuji
>

Re: New GIT net tree naming...

[David Miller]

From: "Ian Brown" <ianbrn@gmail.com>
Date: Mon, 21 Apr 2008 11:13:47 +0300

> Thanks.
> 
> >  git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git
> >  git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next-2.6.git
> 
> OK , these URL worked for me.
> 
> last question:
> 
> Do I understand correctly - patches sent for this mailing list from
> now on are for davem/net-2.6.git tree and not for the
> davem/net-next-2.6.git ? or they can be for both, and we can
> understand from the patch title to which git tree they are ?

We're only accepting bug fixes now and they will go into
davem/net-2.6.git

After some time I'll start accepting feature and other non-bugfix
changes, and those will go into davem/net-next-2.6.git

Re: New GIT net tree naming...

[John W. Linville]

On Sat, Apr 19, 2008 at 05:35:10PM -0700, David Miller wrote:
> 
> Based upon feedback from Andrew and others I'm now starting
> to use a new naming scheme for my GIT trees:
> 
> For changes against Linus's current tree:
> 
>    master.kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6.git
> 
> For development meant to be merged in the next merge
> window we have:
> 
>    master.kernel.org:/pub/scm/linux/kernel/git/davem/net-next-2.6.git
> 
> Andrew/Stephen, let me know if this works for you.  This way
> the tree names will never change.

I have adopted this same scheme for wireless as well:

For changes against Linus's current tree:

   master.kernel.org:/pub/scm/linux/kernel/git/linville/wireless-2.6.git

For development meant to be merged in the next merge
window we have:

   master.kernel.org:/pub/scm/linux/kernel/git/linville/wireless-next-2.6.git

John
-- 
John W. Linville
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: New GIT net tree naming...

[Holger Schurig]

> For changes against Linus's current tree:
...
> For development meant to be merged in the next merge
> window we have:

Is this relevant for us, the patch submitters?  Or should we 
continue to create patches against wireless-testing?
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: New GIT net tree naming...

[John W. Linville]

On Thu, May 08, 2008 at 09:06:29AM +0200, Holger Schurig wrote:
> > For changes against Linus's current tree:
> ...
> > For development meant to be merged in the next merge
> > window we have:
> 
> Is this relevant for us, the patch submitters?  Or should we 
> continue to create patches against wireless-testing?

Please continue to use wireless-testing.

Thanks!

JOhn
-- 
John W. Linville
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: New GIT net tree naming...

[Tomas Winkler]

On Thu, May 8, 2008 at 5:40 PM, John W. Linville <linville@tuxdriver.com> wrote:
> On Thu, May 08, 2008 at 09:06:29AM +0200, Holger Schurig wrote:
>> > For changes against Linus's current tree:
>> ...
>> > For development meant to be merged in the next merge
>> > window we have:
>>
>> Is this relevant for us, the patch submitters?  Or should we
>> continue to create patches against wireless-testing?
>
> Please continue to use wireless-testing.
>
> Thanks!
>
John
How would you want me to handle bug fixes to go both directions
wireless-testing and upstream?
Because of huge code movement we are now doing in iwlwifi they are
currently just not the same.
Shell I send two versions or you want to back port them not sure how
do you want to track this...somewhere in merging loop it will create a
conflict.  Maybe this is maintainer trivia anyhow
I would like to make sure there are not glitches.

Thanks
Tomas

Thanks
Tomas

> JOhn
> --
> John W. Linville
> linville@tuxdriver.com
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: New GIT net tree naming...

[John W. Linville]

On Mon, May 12, 2008 at 08:39:22PM +0300, Tomas Winkler wrote:

> How would you want me to handle bug fixes to go both directions
> wireless-testing and upstream?
> Because of huge code movement we are now doing in iwlwifi they are
> currently just not the same.
> Shell I send two versions or you want to back port them not sure how
> do you want to track this...somewhere in merging loop it will create a
> conflict.  Maybe this is maintainer trivia anyhow
> I would like to make sure there are not glitches.

It is a good question -- thanks for asking!

If you think that two versions of the fix are appropriate, then please
do send them.  If it is simply because the code moved I'll probably
be able to figure it out, but if the code has actually changed it
may be worthwhile.

We are now trying to avoid rebasing "-next" patches as much as possible.
So the version for the current release will be merged to Linus and I or
Dave will have to figure-out how to resolve the merge conflicts when
current is pulled to -next.  Providing a "-next' version of the patch
can help to make sure that those merge conflicts are handled correctly.

John
-- 
John W. Linville
linville@tuxdriver.com

Re: New GIT net tree naming...

[Tomas Winkler]

On Mon, May 12, 2008 at 9:47 PM, John W. Linville
<linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org> wrote:
> On Mon, May 12, 2008 at 08:39:22PM +0300, Tomas Winkler wrote:
>
>  > How would you want me to handle bug fixes to go both directions
>  > wireless-testing and upstream?
>  > Because of huge code movement we are now doing in iwlwifi they are
>  > currently just not the same.
>  > Shell I send two versions or you want to back port them not sure how
>  > do you want to track this...somewhere in merging loop it will create a
>  > conflict.  Maybe this is maintainer trivia anyhow
>  > I would like to make sure there are not glitches.
>
>  It is a good question -- thanks for asking!
>
>  If you think that two versions of the fix are appropriate, then please
>  do send them.  If it is simply because the code moved I'll probably
>  be able to figure it out, but if the code has actually changed it
>  may be worthwhile.
>
>  We are now trying to avoid rebasing "-next" patches as much as possible.
>  So the version for the current release will be merged to Linus and I or
>  Dave will have to figure-out how to resolve the merge conflicts when
>  current is pulled to -next.  Providing a "-next' version of the patch
>  can help to make sure that those merge conflicts are handled correctly.
>
>  John

I'm not able to clone neither wireless-2.6.git nor net-2.6.git through http
I'm behind a firewall so git protocol is not an option


git-clone  ttp://www.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git
Initialized empty Git repository in ....
Cannot get remote repository information.
Perhaps git-update-server-info needs to be run there?

git-clone  http://www.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.gi
Getting pack list for
http://www.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git
Getting index for pack 1c206683ae18d8f0b4833dcee50c8e1c76832df9
Getting pack list for
http://www.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git/
error: Unable to find 090b293b87792a815cf51aeccb590ec37c90cfa3 under
http://www.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git
Cannot obtain needed blob 090b293b87792a815cf51aeccb590ec37c90cfa3
while processing commit 6e40a915de82e00d18f75941e531b40c4e0d94c4.
Waiting for http://www.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git//objects/9a/eb872460a5dcab8b4baf13125d0177f865f393
got 334974abd063c20dc64dd32724425be36b90cebc
got 9aeb872460a5dcab8b4baf13125d0177f865f393
Waiting for http://www.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git//objects/ab/ef366d1ab8fe2ac484039976600938f6c76db3
Received DONE message for unknown request!


Thanks
Tomas
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: New GIT net tree naming...

[John W. Linville]

On Tue, May 13, 2008 at 01:05:22PM +0300, Tomas Winkler wrote:

> I'm not able to clone neither wireless-2.6.git nor net-2.6.git through http
> I'm behind a firewall so git protocol is not an option
> 
> 
> git-clone  ttp://www.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git
> Initialized empty Git repository in ....
> Cannot get remote repository information.
> Perhaps git-update-server-info needs to be run there?
> 
> git-clone  http://www.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.gi
> Getting pack list for
> http://www.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git
> Getting index for pack 1c206683ae18d8f0b4833dcee50c8e1c76832df9
> Getting pack list for
> http://www.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git/
> error: Unable to find 090b293b87792a815cf51aeccb590ec37c90cfa3 under
> http://www.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git
> Cannot obtain needed blob 090b293b87792a815cf51aeccb590ec37c90cfa3
> while processing commit 6e40a915de82e00d18f75941e531b40c4e0d94c4.
> Waiting for http://www.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git//objects/9a/eb872460a5dcab8b4baf13125d0177f865f393
> got 334974abd063c20dc64dd32724425be36b90cebc
> got 9aeb872460a5dcab8b4baf13125d0177f865f393
> Waiting for http://www.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git//objects/ab/ef366d1ab8fe2ac484039976600938f6c76db3
> Received DONE message for unknown request!

I got a similar message when trying to clone using http://.  I was
able to clone using git:// without a problem.

FWIW I have the post-update hook enabled, and I didn't change my
normal practices for publishing trees on kernel.org.  I'm not sure
what is happening.  Anyone have an idea as to what is happening?

John
-- 
John W. Linville
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: New GIT net tree naming...

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 703 bytes --]

Hi John,

On Wed, 7 May 2008 21:43:58 -0400 "John W. Linville" <linville-2XuSBdqkA4SvXiR4WA35Jg@public.gmane.orgm> wrote:
>
> I have adopted this same scheme for wireless as well:
> 
> For changes against Linus's current tree:
> 
>    master.kernel.org:/pub/scm/linux/kernel/git/linville/wireless-2.6.git

This is now wireless-current in linux-next.

> For development meant to be merged in the next merge
> window we have:
> 
>    master.kernel.org:/pub/scm/linux/kernel/git/linville/wireless-next-2.6.git

This is now wireless in linux-next.

Thanks.
-- 
Cheers,
Stephen Rothwell                    sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]