netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junio@pobox.com>
To: Divy Le Ray <divy@chelsio.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	swise@opengridcomputing.com, wenxiong@us.ibm.com
Subject: Re: [PATCH 2/2] cxgb3 - Parity initialization for T3C adapters
Date: Tue, 11 Dec 2007 14:27:55 -0800	[thread overview]
Message-ID: <7vbq8wdfys.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <4759CD92.2070604@chelsio.com> (Divy Le Ray's message of "Fri, 07 Dec 2007 14:47:46 -0800")

Divy Le Ray <divy@chelsio.com> writes:

> On this topic, I have a question: how do I get to see all the
> netdev-2.6 branches ?
> After cloning a free  netdev-2.6 tree, 'git branch' shows only the
> master branch:
> ...
> Cloning
> "git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git"
> into "netdev-2.6-fresh"...
> Initialized empty Git repository in /opt/sources/netdev-2.6-fresh/.git/
> ...
> 100% (23058/23058) done
> done
> -bash-3.1$ cd netdev-2.6-fresh/
> -bash-3.1$ git branch
> * master

At this point,

$ git branch -r

will show you have copies of Jeff's branches in remotes/origin/.

$ git checkout -b upstream origin/upstream

would make your local upstream branch that forks from Jeff's upstream
branch.

      parent reply	other threads:[~2007-12-11 22:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-05 18:15 [PATCH 2/2] cxgb3 - Parity initialization for T3C adapters Divy Le Ray
2007-12-07 20:02 ` Jeff Garzik
2007-12-07 22:47   ` Divy Le Ray
2007-12-07 23:26     ` Jeff Garzik
2007-12-08  0:14       ` Divy Le Ray
2007-12-14 23:05         ` Divy Le Ray
2007-12-11 22:27     ` Junio C Hamano [this message]

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=7vbq8wdfys.fsf@gitster.siamese.dyndns.org \
    --to=junio@pobox.com \
    --cc=divy@chelsio.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=swise@opengridcomputing.com \
    --cc=wenxiong@us.ibm.com \
    /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).