<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/Documentation/git-clone.txt, branch v2.29.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.29.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.29.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2020-09-17T18:30:05Z</updated>
<entry>
<title>maintenance: replace run_auto_gc()</title>
<updated>2020-09-17T18:30:05Z</updated>
<author>
<name>Derrick Stolee</name>
<email>dstolee@microsoft.com</email>
</author>
<published>2020-09-17T18:11:44Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=a95ce124305adcc4980241b8877e06db1d6ed411'/>
<id>urn:sha1:a95ce124305adcc4980241b8877e06db1d6ed411</id>
<content type='text'>
The run_auto_gc() method is used in several places to trigger a check
for repo maintenance after some Git commands, such as 'git commit' or
'git fetch'.

To allow for extra customization of this maintenance activity, replace
the 'git gc --auto [--quiet]' call with one to 'git maintenance run
--auto [--quiet]'. As we extend the maintenance builtin with other
steps, users will be able to select different maintenance activities.

Rename run_auto_gc() to run_auto_maintenance() to be clearer what is
happening on this call, and to expose all callers in the current diff.
Rewrite the method to use a struct child_process to simplify the calls
slightly.

Since 'git fetch' already allows disabling the 'git gc --auto'
subprocess, add an equivalent option with a different name to be more
descriptive of the new behavior: '--[no-]maintenance'. Update the
documentation to include these options at the same time.

Signed-off-by: Derrick Stolee &lt;dstolee@microsoft.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>docs: add missing diamond brackets</title>
<updated>2020-06-24T16:14:21Z</updated>
<author>
<name>Johannes Schindelin</name>
<email>johannes.schindelin@gmx.de</email>
</author>
<published>2020-06-24T14:46:31Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=6069eccdc9d6351f1668b85551bbee4b6ca7cbb0'/>
<id>urn:sha1:6069eccdc9d6351f1668b85551bbee4b6ca7cbb0</id>
<content type='text'>
There were a couple of instances in our manual pages that had an
opening diamond bracket without a corresponding closing one.

Signed-off-by: Johannes Schindelin &lt;johannes.schindelin@gmx.de&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>clone: document --filter options</title>
<updated>2020-03-22T23:38:30Z</updated>
<author>
<name>Derrick Stolee</name>
<email>dstolee@microsoft.com</email>
</author>
<published>2020-03-22T19:50:06Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=4a465443a6ce51bd6e1d4ffef56d3f2e8d45f506'/>
<id>urn:sha1:4a465443a6ce51bd6e1d4ffef56d3f2e8d45f506</id>
<content type='text'>
It turns out that the "--filter=&lt;filter-spec&gt;" option is not
documented anywhere in the "git clone" page, and instead is
detailed carefully in "git rev-list" where it serves a
different purpose.

Add a small bit about this option in the documentation. It
would be worth some time to create a subsection in the "git clone"
documentation about partial clone as a concept and how it can be
a surprising experience. For example, "git checkout" will likely
trigger a pack download.

Signed-off-by: Derrick Stolee &lt;dstolee@microsoft.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'ja/doc-markup-cleanup'</title>
<updated>2019-12-25T19:22:00Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2019-12-25T19:22:00Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=dfee504bee4353fd7cede8b11e0090e20c69a032'/>
<id>urn:sha1:dfee504bee4353fd7cede8b11e0090e20c69a032</id>
<content type='text'>
Doc cleanup.

* ja/doc-markup-cleanup:
  doc: indent multi-line items in list
  doc: remove non pure ASCII characters
</content>
</entry>
<entry>
<title>doc: remove non pure ASCII characters</title>
<updated>2019-12-13T20:18:05Z</updated>
<author>
<name>Jean-Noël Avila</name>
<email>jn.avila@free.fr</email>
</author>
<published>2019-12-12T20:46:54Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=fd5041e127dbe6b5974c924d2386ee2a2ce8b2ce'/>
<id>urn:sha1:fd5041e127dbe6b5974c924d2386ee2a2ce8b2ce</id>
<content type='text'>
Non ASCII characters may be handled by publishing chains, but right
now, nothing indicates the encoding of files. Moreover, non ASCII
source strings upset the localization toolchain.

Signed-off-by: Jean-Noël Avila &lt;jn.avila@free.fr&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>clone: add --sparse mode</title>
<updated>2019-11-22T07:11:43Z</updated>
<author>
<name>Derrick Stolee</name>
<email>dstolee@microsoft.com</email>
</author>
<published>2019-11-21T22:04:35Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=d89f09c8289a764f0a974e02bd5b38cf60d1a7d7'/>
<id>urn:sha1:d89f09c8289a764f0a974e02bd5b38cf60d1a7d7</id>
<content type='text'>
When someone wants to clone a large repository, but plans to work
using a sparse-checkout file, they either need to do a full
checkout first and then reduce the patterns they included, or
clone with --no-checkout, set up their patterns, and then run
a checkout manually. This requires knowing a lot about the repo
shape and how sparse-checkout works.

Add a new '--sparse' option to 'git clone' that initializes the
sparse-checkout file to include the following patterns:

	/*
	!/*/

These patterns include every file in the root directory, but
no directories. This allows a repo to include files like a
README or a bootstrapping script to grow enlistments from that
point.

During the 'git sparse-checkout init' call, we must first look
to see if HEAD is valid, since 'git clone' does not have a valid
HEAD at the point where it initializes the sparse-checkout. The
following checkout within the clone command will create the HEAD
ref and update the working directory correctly.

Signed-off-by: Derrick Stolee &lt;dstolee@microsoft.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'qn/clone-doc-use-long-form'</title>
<updated>2019-07-11T22:16:48Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2019-07-11T22:16:48Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=4ad01a4c9fa42d389dc3da7c17adaf334735a3a8'/>
<id>urn:sha1:4ad01a4c9fa42d389dc3da7c17adaf334735a3a8</id>
<content type='text'>
The "git clone" documentation refers to command line options in its
description in the short form; they have been replaced with long
forms to make them more recognisable.

* qn/clone-doc-use-long-form:
  docs: git-clone: list short form of options first
  docs: git-clone: refer to long form of options
</content>
</entry>
<entry>
<title>docs: git-clone: list short form of options first</title>
<updated>2019-07-02T19:11:40Z</updated>
<author>
<name>Quentin Nerden</name>
<email>quentin.nerden@intel.com</email>
</author>
<published>2019-07-02T14:37:41Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=bfc8c84ed560af8f74be32fa0fd2568e28161678'/>
<id>urn:sha1:bfc8c84ed560af8f74be32fa0fd2568e28161678</id>
<content type='text'>
List the short form of options (e.g.: '-l') before the long form (e.g.
'--local').
This is to match the doc of git-add, git-commit, git-clean, git-branch...

Signed-off-by: Quentin Nerden &lt;quentin.nerden@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>docs: git-clone: refer to long form of options</title>
<updated>2019-07-02T19:11:38Z</updated>
<author>
<name>Quentin Nerden</name>
<email>quentin.nerden@intel.com</email>
</author>
<published>2019-07-02T14:37:40Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=3711d1cd8984d69b61b3a3626aa88ba52fa32d48'/>
<id>urn:sha1:3711d1cd8984d69b61b3a3626aa88ba52fa32d48</id>
<content type='text'>
To make the doc of git-clone easier to read,
refer to the long form of the options
(it is easier to guess what '--verbose' is doing than '-v').

Signed-off-by: Quentin Nerden &lt;quentin.nerden@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>clone: add `--remote-submodules` flag</title>
<updated>2019-05-28T16:22:02Z</updated>
<author>
<name>Ben Avison</name>
<email>bavison@riscosopen.org</email>
</author>
<published>2019-05-19T14:26:49Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=4c6910163ab59f334becca39f5a83d3b7a622df4'/>
<id>urn:sha1:4c6910163ab59f334becca39f5a83d3b7a622df4</id>
<content type='text'>
When using `git clone --recurse-submodules` there was previously no way to
pass a `--remote` switch to the implicit `git submodule update` command for
any use case where you want the submodules to be checked out on their
remote-tracking branch rather than with the SHA-1 recorded in the superproject.

This patch rectifies this situation. It actually passes `--no-fetch` to
`git submodule update` as well on the grounds they the submodule has only just
been cloned, so fetching from the remote again only serves to slow things down.

Signed-off-by: Ben Avison &lt;bavison@riscosopen.org&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
</feed>
