From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: "Victor Gallardo" <vgallardo@amcc.com>
Cc: linuxppc-dev@ozlabs.org, Feng Kan <fkan@amcc.com>
Subject: Re: [PATCH v2] Add AMCC Arches eval board support to platforms/44x
Date: Tue, 23 Sep 2008 08:21:43 -0400 [thread overview]
Message-ID: <20080923082143.7b00bfbc@zod.rchland.ibm.com> (raw)
In-Reply-To: <0CA0A16855646F4FA96D25A158E299D6050D1CEF@SDCEXCHANGE01.ad.amcc.com>
On Mon, 22 Sep 2008 16:54:46 -0700
"Victor Gallardo" <vgallardo@amcc.com> wrote:
> Hi Josh,
>
> >
> >You need to look in the 'next' branch.
> >
> > http://git.kernel.org/?p=linux/kernel/git/jwboyer/powerpc-4xx.git;a=tree;f=arch/powerpc/platforms/44x;h=c5cae8d37f170193ed45b7b76e3cb2cbb8be927a;hb=next
> >
> >josh
>
> I am not sure how to get your next branch.
>
> I usually just use the following command.
>
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/jwboyer/powerpc-4xx.git linux-ppc4xx
This is fine.
> How do I get the next branch?
'git branch -r' will show you all the remote branches. To check out
the 'next' branch, simply do:
'git checkout -b next origin/next'
My setup is slightly different because I clone Linus' tree and add
Paul's and my own as remotes using 'git remote add'. But that's just
how I prefer to operate, and there is nothing wrong with cloning my
tree itself if you are only looking for 4xx changes.
josh
prev parent reply other threads:[~2008-09-23 12:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 22:47 [PATCH v2] Add AMCC Arches eval board support to platforms/44x Victor Gallardo
2008-09-19 0:01 ` Josh Boyer
2008-09-19 0:01 ` Josh Boyer
2008-09-19 17:31 ` Victor Gallardo
2008-09-19 17:39 ` Josh Boyer
2008-09-22 23:54 ` Victor Gallardo
2008-09-23 12:21 ` Josh Boyer [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=20080923082143.7b00bfbc@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=fkan@amcc.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=vgallardo@amcc.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).