<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/Documentation/git-pack-objects.txt, branch v1.6.3</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v1.6.3</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v1.6.3'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2008-11-12T18:29:22Z</updated>
<entry>
<title>pack-objects: extend --local to mean ignore non-local loose objects too</title>
<updated>2008-11-12T18:29:22Z</updated>
<author>
<name>Brandon Casey</name>
<email>drafnel@gmail.com</email>
</author>
<published>2008-11-10T05:59:58Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=daae06259556246959963947752bde4ee2df7b44'/>
<id>urn:sha1:daae06259556246959963947752bde4ee2df7b44</id>
<content type='text'>
With this patch, --local means pack only local objects that are not already
packed.

Additionally, this fixes t7700 testing whether loose objects in an alternate
object database are repacked.

Signed-off-by: Brandon Casey &lt;drafnel@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>pack-objects: new option --honor-pack-keep</title>
<updated>2008-11-12T18:28:10Z</updated>
<author>
<name>Brandon Casey</name>
<email>casey@nrlssc.navy.mil</email>
</author>
<published>2008-11-12T17:59:04Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=e96fb9b8f90f907d720ea6b71c92e30c2b071f4a'/>
<id>urn:sha1:e96fb9b8f90f907d720ea6b71c92e30c2b071f4a</id>
<content type='text'>
This adds a new option to pack-objects which will cause it to ignore an
object which appears in a local pack which has a .keep file, even if it
was specified for packing.

This option will be used by the porcelain repack.

Signed-off-by: Brandon Casey &lt;casey@nrlssc.navy.mil&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>manpages: italicize git command names (which were in teletype font)</title>
<updated>2008-07-05T18:24:40Z</updated>
<author>
<name>Jonathan Nieder</name>
<email>jrnieder@uchicago.edu</email>
</author>
<published>2008-07-03T05:41:41Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=ba020ef5eb5fca3d757bd580ff117adaf81ca079'/>
<id>urn:sha1:ba020ef5eb5fca3d757bd580ff117adaf81ca079</id>
<content type='text'>
The names of git commands are not meant to be entered at the
commandline; they are just names. So we render them in italics,
as is usual for command names in manpages.

Using

	doit () {
	  perl -e 'for (&lt;&gt;) { s/\`(git-[^\`.]*)\`/'\''\1'\''/g; print }'
	}
	for i in git*.txt config.txt diff*.txt blame*.txt fetch*.txt i18n.txt \
	        merge*.txt pretty*.txt pull*.txt rev*.txt urls*.txt
	do
	  doit &lt;"$i" &gt;"$i+" &amp;&amp; mv "$i+" "$i"
	done
	git diff

.

Signed-off-by: Jonathan Nieder &lt;jrnieder@uchicago.edu&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Documentation formatting and cleanup</title>
<updated>2008-07-02T00:20:16Z</updated>
<author>
<name>Jonathan Nieder</name>
<email>jrnieder@uchicago.edu</email>
</author>
<published>2008-06-30T18:56:34Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=483bc4f045881b998512ae814d6cf44d0c0cb493'/>
<id>urn:sha1:483bc4f045881b998512ae814d6cf44d0c0cb493</id>
<content type='text'>
Following what appears to be the predominant style, format
names of commands and commandlines both as `teletype text`.

While we're at it, add articles ("a" and "the") in some
places, italicize the name of the command in the manual page
synopsis line, and add a comma or two where it seems appropriate.

Signed-off-by: Jonathan Nieder &lt;jrnieder@uchicago.edu&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Documentation: be consistent about "git-" versus "git "</title>
<updated>2008-07-02T00:20:15Z</updated>
<author>
<name>Jonathan Nieder</name>
<email>jrnieder@uchicago.edu</email>
</author>
<published>2008-06-30T06:09:04Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=b1889c36d85514e5e70462294c561a02c2edfe2b'/>
<id>urn:sha1:b1889c36d85514e5e70462294c561a02c2edfe2b</id>
<content type='text'>
Since the git-* commands are not installed in $(bindir), using
"git-command &lt;parameters&gt;" in examples in the documentation is
not a good idea. On the other hand, it is nice to be able to
refer to each command using one hyphenated word. (There is no
escaping it, anyway: man page names cannot have spaces in them.)

This patch retains the dash in naming an operation, command,
program, process, or action. Complete command lines that can
be entered at a shell (i.e., without options omitted) are
made to use the dashless form.

The changes consist only of replacing some spaces with hyphens
and vice versa. After a "s/ /-/g", the unpatched and patched
versions are identical.

Signed-off-by: Jonathan Nieder &lt;jrnieder@uchicago.edu&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Docs: Use "-l::\n--long\n" format in OPTIONS sections</title>
<updated>2008-06-08T20:46:38Z</updated>
<author>
<name>Stephan Beyer</name>
<email>s-beyer@gmx.net</email>
</author>
<published>2008-06-08T01:36:09Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=3240240ff427fa2e26a847c7c9fd89e6a4313daa'/>
<id>urn:sha1:3240240ff427fa2e26a847c7c9fd89e6a4313daa</id>
<content type='text'>
The OPTIONS section of a documentation file contains a list
of the options a git command accepts.

Currently there are several variants to describe the case that
different options (almost) do the same in the OPTIONS section.

Some are:

 -f, --foo::
 -f|--foo::
 -f | --foo::

But AsciiDoc has the special form:

 -f::
 --foo::

This patch applies this form to the documentation of the whole git suite,
and removes useless em-dash prevention, so \--foo becomes --foo.

Signed-off-by: Stephan Beyer &lt;s-beyer@gmx.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>documentation: move git(7) to git(1)</title>
<updated>2008-06-06T18:18:28Z</updated>
<author>
<name>Christian Couder</name>
<email>chriscool@tuxfamily.org</email>
</author>
<published>2008-06-06T07:07:32Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=9e1f0a85c68323830ea117092c55192b17aa3ac8'/>
<id>urn:sha1:9e1f0a85c68323830ea117092c55192b17aa3ac8</id>
<content type='text'>
As the "git" man page describes the "git" command at the end-user
level, it seems better to move it to man section 1.

Signed-off-by: Christian Couder &lt;chriscool@tuxfamily.org&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Manual subsection to refer to other pages is SEE ALSO</title>
<updated>2008-05-28T23:59:40Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2008-05-28T23:55:27Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=56ae8df5c7b05ee8982c9447fa31116104dc568f'/>
<id>urn:sha1:56ae8df5c7b05ee8982c9447fa31116104dc568f</id>
<content type='text'>
Consistently say so in all caps as it is customary to do so.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>git-pack-objects.txt: Make wording slightly less ambiguous</title>
<updated>2008-04-05T23:51:16Z</updated>
<author>
<name>Peter Eriksen</name>
<email>s022018@student.dtu.dk</email>
</author>
<published>2008-04-05T19:46:49Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=ba1333fec3df7496839106ee8730939d100d989d'/>
<id>urn:sha1:ba1333fec3df7496839106ee8730939d100d989d</id>
<content type='text'>
It is a bit confusing on first read, that

        "The packed archive format (.pack) is designed
        to be unpackable..."

Signed-off-by: Peter Eriksen &lt;s022018@student.dtu.dk&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>git-pack-objects: Automatically pack annotated tags if object was packed</title>
<updated>2008-03-05T07:28:14Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2008-03-04T03:27:20Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=f0a24aa56e49a5cb03101ead0211c7080b96c9f1'/>
<id>urn:sha1:f0a24aa56e49a5cb03101ead0211c7080b96c9f1</id>
<content type='text'>
The new option "--include-tag" allows the caller to request that
any annotated tag be included into the packfile if the object the tag
references was also included as part of the packfile.

This option can be useful on the server side of a native git transport,
where the server knows what commits it is including into a packfile to
update the client.  If new annotated tags have been introduced then we
can also include them in the packfile, saving the client from needing
to request them through a second connection.

This change only introduces the backend option and provides a test.
Protocol extensions to make this useful in fetch-pack/upload-pack
are still necessary to activate the logic during transport.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
</feed>
