Geert Uytterhoeven <[email protected]> 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, [email protected] GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
