From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Kolbjørn Barmen" <linux-m68k@kolla.no>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: How to get m68k sources?
Date: Sat, 11 Apr 2009 10:16:29 +0200 [thread overview]
Message-ID: <10f740e80904110116j6626b564m92b0fbf9fca79106@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.0904102301250.22946@halbrend.uninett.no>
2009/4/10 Kolbjørn Barmen <linux-m68k@kolla.no>:
> Just wondering, what is the current procedure to get the current
> "release" (or snapshot) sources, for example 2.6.29 for m68k?
> I have used git before, allthough not much, but I have not figured out
> what to pull from where, and how to integrate the lot. A simple
> step-by-step how-to would be nice.
git clone git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git
gives you a copy of the Linux/m68k repository. The default (branch `master')
is the current development tree (v2.6.30-rc1 for now).
2.6.29 development is done on branch `m68k-v2.6.29', use
git checkout m68k-v2.6.29
If you want to update later, simply do (if you're not on branch
`master', you'll have to
do `checkout master' first):
git pull
If you already have a copy of Linus' repository around, you can save diskspace
and download bandwidth by
1. Adding `--reference <path-to-your-copy-of-Linus'-repository' to the
`git clone' command (if you want a separate repository for m68k)
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
If you have more questions, feel free to ask!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" 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:[~2009-04-11 8:16 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 [this message]
2009-04-11 10:14 ` Andreas Schwab
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=10f740e80904110116j6626b564m92b0fbf9fca79106@mail.gmail.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox