2009/4/11 Andreas Schwab <schwab@xxxxxxxxxxxxxx>:
Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> 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.
You can do without a tracking branch, i.e. `git checkout
linux-m68k/m68k-v2.6.29'
does work. But for my first example above (separate clone) I forgot
the `origin/',
so that had to be:
git checkout origin/m68k-v2.6.29
But if you want to do (and check-in) actual development, and update regularly,
it's indeed better to have the tracking branches. Thanks for the update!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
