# --------------{ x86.git instructions }---------->

mkdir linux.trees.git || exit -1
cd linux.trees.git

git-init-db
# Add Linus's tree as a remote
git-remote add linus git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git

# Add the x86 tree as a remote
git-remote add x86 git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git

#
# With that setup, just run the following to get any changes you
# don't have.  It will also notice any new branches Ingo/Linus
# add to their repo.  Look in .git/config afterwards, the format
# to add new remotes is easy to figure out.
#
# This will take a lot of time initially (it downloads the ~150MB
# repository), but will be much faster subsequently as it only
# does delta updates. Note that it may warn you about no common
# commits but you can ignore that:
# 
git-remote update

#
# Check out the latest x86 testing-branch to a local branch
# in this example, we create a branch called 'x86-latest'
# You can pick whatever name suits you.
#
git-checkout -b x86-latest x86/master

#
# if you need to do bisection of the x86 tree, then do:
# (but first check that linus/master is indeed a 'good' kernel :-)
#
git-bisect start
git-bisect good linus/master
git-bisect bad x86/master

#
# If you want to help out with cleanups, and want to pick some
# low hanging fruits, do this:
#
wget http://redhat.com/~mingo/x86.git/code-quality
chmod +x code-quality

./code-quality `find arch/x86 include/asm-x86/ -name '*.c'` | tee quality.txt

#
# Pick the file that looks most interesting to you:
#
sort -n -k 4 quality.txt

#
# and if you do some work based on x86.git, feel free to talk
# to the maintainers about it (especially if you are about to
# do some bigger chunk of work and think that you'd like to
# ask whether it makes sense or whether anyone else is working
# on it):
#
#  X86 ARCHITECTURE (32-BIT AND 64-BIT)
#  P:      Thomas Gleixner
#  M:      tglx@linutronix.de
#  P:      Ingo Molnar
#  M:      mingo@redhat.com
#  P:      H. Peter Anvin
#  M:      hpa@zytor.com
#
# And this is the mailing list to send patches to:
#
#  L:      linux-kernel@vger.kernel.org
#
# When sending arch/x86 patches, please try to use the following
# subject line format (sample):
#
# Subject: [patch] x86: fix typo ...
#