All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Kolbjørn Barmen" <linux-m68k@kolla.no>,
	Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: How to get m68k sources?
Date: Sat, 11 Apr 2009 12:14:49 +0200	[thread overview]
Message-ID: <m2ab6nts2u.fsf@igel.home> (raw)
In-Reply-To: <10f740e80904110116j6626b564m92b0fbf9fca79106@mail.gmail.com> (Geert Uytterhoeven's message of "Sat, 11 Apr 2009 10:16:29 +0200")

Geert Uytterhoeven <geert@linux-m68k.org> writes:

> 2.6.29 development is done on branch `m68k-v2.6.29', use
>
>     git checkout m68k-v2.6.29

After cloning the repository you first have to create the tracking
m68k-v2.6.29 branch:

$ git checkout -t origin/m68k-v2.6.29

>   2. Set up a remote (if you want a combined one with Linus' and m68k):
>
>     git remote add linux-m68k
> git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git
>     git remote update
>     git checkout linux-m68k/master
> or  git checkout linux-m68k/m68k-v2.6.29

Same here, you need to add -t to the checkout commands to tell git to
create tracking branches.  In the first case when checking out
linux-m68k/master you also have to add "-b <branch>" to name the local
branch differently from the already existing master branch.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2009-04-11 10:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-10 21:09 How to get m68k sources? Kolbjørn Barmen
2009-04-11  8:16 ` Geert Uytterhoeven
2009-04-11 10:14   ` Andreas Schwab [this message]
2009-04-12  4:35     ` Kolbjørn Barmen
2009-04-12  6:18       ` Kolbjørn Barmen
2009-04-13  2:20         ` Kolbjørn Barmen
2009-04-13 12:48           ` Kolbjørn Barmen
2009-04-12  6:53       ` Andreas Schwab
2009-04-12  8:29       ` Geert Uytterhoeven
2009-04-12  8:25     ` Geert Uytterhoeven
2009-04-12 12:36       ` Andreas Schwab

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=m2ab6nts2u.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@kolla.no \
    --cc=linux-m68k@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.