From: "Ian Brown" <ianbrn@gmail.com>
To: "David Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: New GIT net tree naming...
Date: Mon, 21 Apr 2008 10:53:16 +0300 [thread overview]
Message-ID: <d0383f90804210053w538c20dfp6495072632320abe@mail.gmail.com> (raw)
In-Reply-To: <20080419.173510.257216556.davem@davemloft.net>
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
>
next prev parent reply other threads:[~2008-04-21 7:53 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 [this message]
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
[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=d0383f90804210053w538c20dfp6495072632320abe@mail.gmail.com \
--to=ianbrn@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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).