<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/Documentation/git-pack-objects.txt, branch v2.0.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.0.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.0.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2014-03-11T20:32:10Z</updated>
<entry>
<title>upload-pack: send shallow info over stdin to pack-objects</title>
<updated>2014-03-11T20:32:10Z</updated>
<author>
<name>Nguyễn Thái Ngọc Duy</name>
<email>pclouds@gmail.com</email>
</author>
<published>2014-03-11T12:59:46Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=b790e0f67cd97f29b72cb9007632b0329e5eebec'/>
<id>urn:sha1:b790e0f67cd97f29b72cb9007632b0329e5eebec</id>
<content type='text'>
Before cdab485 (upload-pack: delegate rev walking in shallow fetch to
pack-objects - 2013-08-16) upload-pack does not write to the source
repository. cdab485 starts to write $GIT_DIR/shallow_XXXXXX if it's a
shallow fetch, so the source repo must be writable.

git:// servers do not need write access to repos and usually don't
have it, which means cdab485 breaks shallow clone over git://

Instead of using a temporary file as the media for shallow points, we
can send them over stdin to pack-objects as well. Prepend shallow
SHA-1 with --shallow so pack-objects knows what is what.

Signed-off-by: Nguyễn Thái Ngọc Duy &lt;pclouds@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>pack-objects doc: treat output filename as opaque</title>
<updated>2013-12-16T19:36:09Z</updated>
<author>
<name>Jeff King</name>
<email>peff@peff.net</email>
</author>
<published>2013-12-16T19:19:33Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=40a4f5a7bf0ffee4fa1fb954b1ebf5daba5bae75'/>
<id>urn:sha1:40a4f5a7bf0ffee4fa1fb954b1ebf5daba5bae75</id>
<content type='text'>
After 1190a1a (pack-objects: name pack files after trailer hash,
2013-12-05), the SHA-1 used to determine the filename is calculated
differently.  Update the documentation to not guarantee anything more
than that the SHA-1 depends on the pack content somehow.

Hopefully this will discourage readers from depending on the old or
the new calculation.

Reported-by: Michael Haggerty &lt;mhagger@alum.mit.edu&gt;
Signed-off-by: Jeff King &lt;peff@peff.net&gt;
Signed-off-by: Jonathan Nieder &lt;jrnieder@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>The name of the hash function is "SHA-1", not "SHA1"</title>
<updated>2013-04-15T18:08:37Z</updated>
<author>
<name>Thomas Ackermann</name>
<email>th.acker@arcor.de</email>
</author>
<published>2013-04-15T17:49:04Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=d5fa1f1a69f578831179b77893aac480b986e875'/>
<id>urn:sha1:d5fa1f1a69f578831179b77893aac480b986e875</id>
<content type='text'>
Use "SHA-1" instead of "SHA1" whenever we talk about the hash function.
When used as a programming symbol, we keep "SHA1".

Signed-off-by: Thomas Ackermann &lt;th.acker@arcor.de&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Documentation: the name of the system is 'Git', not 'git'</title>
<updated>2013-02-01T21:53:33Z</updated>
<author>
<name>Thomas Ackermann</name>
<email>th.acker@arcor.de</email>
</author>
<published>2013-01-21T19:17:53Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=2de9b71138171dca7279db3b3fe67e868c76d921'/>
<id>urn:sha1:2de9b71138171dca7279db3b3fe67e868c76d921</id>
<content type='text'>
Signed-off-by: Thomas Ackermann &lt;th.acker@arcor.de&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>remove doubled words, e.g., s/to to/to/, and fix related typos</title>
<updated>2011-04-13T18:59:11Z</updated>
<author>
<name>Jim Meyering</name>
<email>jim@meyering.net</email>
</author>
<published>2011-04-13T15:39:40Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=0353a0c4ec91cf2d0a8e209025aa2e1909d05f19'/>
<id>urn:sha1:0353a0c4ec91cf2d0a8e209025aa2e1909d05f19</id>
<content type='text'>
I found that some doubled words had snuck back into projects from which
I'd already removed them, so now there's a "syntax-check" makefile rule in
gnulib to help prevent recurrence.

Running the command below spotted a few in git, too:

  git ls-files | xargs perl -0777 -n \
    -e 'while (/\b(then?|[iao]n|i[fst]|but|f?or|at|and|[dt])\s+\1\b/gims)' \
    -e '{$n=($` =~ tr/\n/\n/ + 1); ($v=$&amp;)=~s/\n/\\n/g;' \
    -e 'print "$ARGV:$n:$v\n"}'

Signed-off-by: Jim Meyering &lt;meyering@redhat.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Sync with 1.7.4.3</title>
<updated>2011-04-03T07:14:16Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2011-04-03T07:14:16Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=8f84c95fb23848fce7f817daa5818f9822ddc0f9'/>
<id>urn:sha1:8f84c95fb23848fce7f817daa5818f9822ddc0f9</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Doc: mention --delta-base-offset is the default for Porcelain commands</title>
<updated>2011-04-03T06:08:13Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2011-04-03T06:08:13Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=c14f3727913a67835ad38d17edcbfe4e1c94e9a7'/>
<id>urn:sha1:c14f3727913a67835ad38d17edcbfe4e1c94e9a7</id>
<content type='text'>
The underlying pack-objects plumbing command still needs an explicit
option from the command line, but these days Porcelain passes the
option, so there is no need for end users to worry about it anymore.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'maint'</title>
<updated>2011-03-30T21:10:41Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2011-03-30T21:10:41Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=17a02998078923f2d62811326d130de991d1a95a'/>
<id>urn:sha1:17a02998078923f2d62811326d130de991d1a95a</id>
<content type='text'>
* maint:
  contrib/thunderbird-patch-inline: do not require bash to run the script
  t8001: check the exit status of the command being tested
  strbuf.h: remove a tad stale docs-in-comment and reference api-doc instead
  Typos: t/README
  Documentation/config.txt: make truth value of numbers more explicit
  git-pack-objects.txt: fix grammatical errors
  parse-remote: replace unnecessary sed invocation
</content>
</entry>
<entry>
<title>git-pack-objects.txt: fix grammatical errors</title>
<updated>2011-03-30T18:43:15Z</updated>
<author>
<name>Stephen Boyd</name>
<email>bebarino@gmail.com</email>
</author>
<published>2011-03-30T09:00:06Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=2f8ee02c49ea2a8b32c22979a65eb81b859bb883'/>
<id>urn:sha1:2f8ee02c49ea2a8b32c22979a65eb81b859bb883</id>
<content type='text'>
Signed-off-by: Stephen Boyd &lt;bebarino@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>doc: drop author/documentation sections from most pages</title>
<updated>2011-03-11T15:59:16Z</updated>
<author>
<name>Jeff King</name>
<email>peff@peff.net</email>
</author>
<published>2011-03-11T05:52:08Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=48bb914ed641fc0880d86b16cbb17c84769c320a'/>
<id>urn:sha1:48bb914ed641fc0880d86b16cbb17c84769c320a</id>
<content type='text'>
The point of these sections is generally to:

  1. Give credit where it is due.

  2. Give the reader an idea of where to ask questions or
     file bug reports.

But they don't do a good job of either case. For (1), they
are out of date and incomplete. A much more accurate answer
can be gotten through shortlog or blame.  For (2), the
correct contact point is generally git@vger, and even if you
wanted to cc the contact point, the out-of-date and
incomplete fields mean you're likely sending to somebody
useless.

So let's drop the fields entirely from all manpages except
git(1) itself. We already point people to the mailing list
for bug reports there, and we can update the Authors section
to give credit to the major contributors and point to
shortlog and blame for more information.

Each page has a "This is part of git" footer, so people can
follow that to the main git manpage.
</content>
</entry>
</feed>
