Lines Matching full:git
26 git clone --depth 1 -b master \
27 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git ~/linux/
43 git fetch --depth 1 origin
45 git checkout --force --detach origin/master
104 'bc', 'binutils' ('ld' et al.), 'bison', 'flex', 'gcc', 'git', 'openssl',
130 partially cloning the Linux stable git repository. This is called a shallow
132 archives<sources_archive>` *and* :ref:`a full git clone<sources_full>` *;
139 git clone --no-checkout --depth 1 -b master \
140 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git ~/linux/
146 git fetch --shallow-exclude=v6.0 origin
152 git remote set-branches --add origin linux-6.1.y
153 git fetch --shallow-exclude=v6.0 origin
159 git checkout --detach origin/master
179 If you cloned the sources with git and anything goes sideways, run ``git
291 not used yet (say 6.2.y), tell git to track it::
293 git remote set-branches --add origin linux-6.2.y
296 version you care about, as git otherwise might retrieve the entire commit
299 git fetch --shallow-exclude=v6.0 origin
305 git checkout --force --detach origin/master
436 sudo apt install bc binutils bison dwarves flex gcc git make openssl \
442 /usr/bin/{bc,bison,flex,gcc,git,openssl,make,perl,pahole}
446 sudo zypper install bc binutils bison dwarves flex gcc git make perl-base \
492 git clone. There is :ref:`more to tell about this method<sources_shallow>` and
494 and :ref:`a full git clone<sources_full>`. And the aspects ':ref:`wouldn't it
515 * This document in most places uses ``git fetch`` with ``--shallow-exclude=``
516 to specify the earliest version you care about (or to be precise: its git
523 * When running ``git fetch``, remember to always specify the oldest version,
525 guide. Otherwise you will risk downloading nearly the entire git history,
530 you change it over time, git will deepen or flatten the history to the
539 In that case run ``git repack -d`` and try again``
542 perform a bisection (v6.2..v6.3), better tell ``git fetch`` to retrieve
543 objects up to three versions earlier (e.g. 6.0): ``git describe`` will then
544 be able to describe most commits just like it would in a full git clone.
561 with ``git revert`` or might provide various patches to try. Sometimes reporters
562 will also be asked to use ``git bisect`` to find the change causing a problem.
563 These things rely on git or are a lot easier and quicker to handle with it.
566 you use ``git clone --depth=1`` to create a shallow clone of the latest mainline
567 codebase git will only retrieve a little more data than downloading the latest
574 from things that rely on git -- but this mainly concerns the section on
581 Downloading the sources using a full git clone
585 nothing that bothers you, instead of a shallow clone perform a full git clone
590 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/clone.bundle \
591 -o linux-stable.git.bundle
592 git clone linux-stable.git.bundle ~/linux/
593 rm linux-stable.git.bundle
595 git remote set-url origin \
596 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
597 git fetch origin
598 git checkout --detach origin/master
607 When cloning the sources using git and checking out origin/master, you often
627 code from the Linux stable git repository. That makes things simpler for this
636 git remote add mainline \
637 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
638 git fetch mainline
639 git checkout --detach mainline/master
641 When doing this with a shallow clone, remember to call ``git fetch`` with one
1003 If you created a shallow-clone with git, remember what the :ref:`section that
1005 slightly different ``git fetch`` command and when switching to another series
1091 …https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/Documentation/admin-guide…