netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tomas Winkler" <tomasw-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "John W. Linville"
	<linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
	"David Miller" <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: "Holger Schurig"
	<hs4233-x6+DxXLjN1AJvtFkdXX2Hg4jNU5vUVPG@public.gmane.org>,
	linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org,
	akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: New GIT net tree naming...
Date: Tue, 13 May 2008 13:05:22 +0300	[thread overview]
Message-ID: <1ba2fa240805130305q207067b0n572b95340a3745d6@mail.gmail.com> (raw)
In-Reply-To: <20080512184715.GA18910-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>

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

  parent reply	other threads:[~2008-05-13 10:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-20  0:35 New GIT net tree naming David Miller
2008-04-21  1:45 ` Stephen Rothwell
2008-04-21  7:53 ` Ian Brown
2008-04-21  7:56   ` David Miller
2008-04-21  8:00   ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-21  8:13     ` Ian Brown
2008-04-21  8:17       ` David Miller
     [not found] ` <20080419.173510.257216556.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2008-05-08  1:43   ` John W. Linville
     [not found]     ` <20080508014358.GE3412-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-05-08  7:06       ` Holger Schurig
     [not found]         ` <200805080906.29603.hs4233-x6+DxXLjN1AJvtFkdXX2Hg4jNU5vUVPG@public.gmane.org>
2008-05-08 14:40           ` John W. Linville
2008-05-12 17:39             ` Tomas Winkler
2008-05-12 18:47               ` John W. Linville
     [not found]                 ` <20080512184715.GA18910-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-05-13 10:05                   ` Tomas Winkler [this message]
     [not found]                     ` <1ba2fa240805130305q207067b0n572b95340a3745d6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-05-13 13:26                       ` John W. Linville
2008-05-08  7:42       ` 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=1ba2fa240805130305q207067b0n572b95340a3745d6@mail.gmail.com \
    --to=tomasw-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
    --cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
    --cc=hs4233-x6+DxXLjN1AJvtFkdXX2Hg4jNU5vUVPG@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).