<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/fetch-pack.c, branch v2.23.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.23.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.23.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2019-07-09T22:25:43Z</updated>
<entry>
<title>Merge branch 'nd/fetch-capability-tweak'</title>
<updated>2019-07-09T22:25:43Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2019-07-09T22:25:43Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=b49d337bfbdd431697161244ff7b2241d9887c9f'/>
<id>urn:sha1:b49d337bfbdd431697161244ff7b2241d9887c9f</id>
<content type='text'>
Protocol capabilities that go over wire should never be translated,
but it was incorrectly marked for translation, which has been
corrected.  The output of protocol capabilities for debugging has
been tweaked a bit.

* nd/fetch-capability-tweak:
  fetch-pack: print server version at the top in -v -v
  fetch-pack: print all relevant supported capabilities with -v -v
  fetch-pack: move capability names out of i18n strings
</content>
</entry>
<entry>
<title>fetch-pack: print server version at the top in -v -v</title>
<updated>2019-06-20T21:01:00Z</updated>
<author>
<name>Nguyễn Thái Ngọc Duy</name>
<email>pclouds@gmail.com</email>
</author>
<published>2019-06-20T11:59:51Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=0e042971011956be86a59fb3b5e0dbf3a127fae5'/>
<id>urn:sha1:0e042971011956be86a59fb3b5e0dbf3a127fae5</id>
<content type='text'>
Before the previous patch, the server version is printed after all the
"Server supports" lines. The previous one puts the version in the middle
of "Server supports" group.

Instead of moving it to the bottom, I move it to the top. Version may
stand out more at the top as we will have even more debug out after
capabilities.

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>fetch-pack: print all relevant supported capabilities with -v -v</title>
<updated>2019-06-20T21:00:59Z</updated>
<author>
<name>Nguyễn Thái Ngọc Duy</name>
<email>pclouds@gmail.com</email>
</author>
<published>2019-06-20T11:59:50Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=5a88583b0b241c335b4baf2ccd9b04bc1650efcb'/>
<id>urn:sha1:5a88583b0b241c335b4baf2ccd9b04bc1650efcb</id>
<content type='text'>
When we check if some capability is supported, we do print something in
verbose mode. Some capabilities are not printed though (and it made me
think it's not supported; I was more used to GIT_TRACE_PACKET) so let's
print them all.

It's a bit more code. And one could argue for printing all supported
capabilities the server sends us. But I think it's still valuable this
way because we see the capabilities that the client cares about.

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>fetch-pack: move capability names out of i18n strings</title>
<updated>2019-06-20T21:00:59Z</updated>
<author>
<name>Nguyễn Thái Ngọc Duy</name>
<email>pclouds@gmail.com</email>
</author>
<published>2019-06-20T11:59:49Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=0778b2931c8d561b02046a80870af7c9f4d14d52'/>
<id>urn:sha1:0778b2931c8d561b02046a80870af7c9f4d14d52</id>
<content type='text'>
This reduces the work on translators since they only have one string to
translate (and I think it's still enough context to translate). It also
makes sure no capability name is translated by accident.

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>object: convert lookup_object() to use object_id</title>
<updated>2019-06-20T17:18:09Z</updated>
<author>
<name>Jeff King</name>
<email>peff@peff.net</email>
</author>
<published>2019-06-20T07:41:14Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=d0229abd93e1115d935b0e55067e29bcc9815ce8'/>
<id>urn:sha1:d0229abd93e1115d935b0e55067e29bcc9815ce8</id>
<content type='text'>
There are no callers left of lookup_object() that aren't just passing us
the "hash" member of a "struct object_id". Let's take the whole struct,
which gets us closer to removing all raw sha1 variables.  It also
matches the existing conversions of lookup_blob(), etc.

The conversions of callers were done by hand, but they're all mechanical
one-liners.

Signed-off-by: Jeff King &lt;peff@peff.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'jt/clone-server-option'</title>
<updated>2019-05-30T17:50:46Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2019-05-30T17:50:46Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=0e5387cd02482a0b7d42e78900cf3c0b13a39ee2'/>
<id>urn:sha1:0e5387cd02482a0b7d42e78900cf3c0b13a39ee2</id>
<content type='text'>
A brown-paper-bag bugfix to a change already in 'master'.

* jt/clone-server-option:
  fetch-pack: send server options after command
</content>
</entry>
<entry>
<title>fetch-pack: send server options after command</title>
<updated>2019-05-28T18:01:07Z</updated>
<author>
<name>Jonathan Tan</name>
<email>jonathantanmy@google.com</email>
</author>
<published>2019-05-22T20:08:22Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=5b204b7df3ed7e97040d40db9d7c31a0a645af15'/>
<id>urn:sha1:5b204b7df3ed7e97040d40db9d7c31a0a645af15</id>
<content type='text'>
Currently, if any server options are specified during a protocol v2
fetch, server options will be sent before "command=fetch". Write server
options to the request buffer in send_fetch_request() so that the
components of the request are sent in the correct order.

The protocol documentation states that the command must come first. The
Git server implementation in serve.c (see process_request() in that
file) tolerates any order of command and capability, which is perhaps
why we haven't noticed this. This was noticed when testing against a
JGit server implementation, which follows the documentation in this
regard.

Signed-off-by: Jonathan Tan &lt;jonathantanmy@google.com&gt;
Acked-by: Jonathan Nieder &lt;jrnieder@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'jk/fetch-reachability-error-fix'</title>
<updated>2019-04-25T07:41:23Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2019-04-25T07:41:23Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=57a6b93236f3b1667a1947d3fc83f6e942d3bfca'/>
<id>urn:sha1:57a6b93236f3b1667a1947d3fc83f6e942d3bfca</id>
<content type='text'>
Code clean-up and a fix for "git fetch" by an explicit object name
(as opposed to fetching refs by name).

* jk/fetch-reachability-error-fix:
  fetch: do not consider peeled tags as advertised tips
  remote.c: make singular free_ref() public
  fetch: use free_refs()
  pkt-line: prepare buffer before handling ERR packets
  upload-pack: send ERR packet for non-tip objects
  t5530: check protocol response for "not our ref"
  t5516: drop ok=sigpipe from unreachable-want tests
</content>
</entry>
<entry>
<title>Merge branch 'jt/fetch-no-update-shallow-in-proto-v2'</title>
<updated>2019-04-25T07:41:16Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2019-04-25T07:41:16Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=732ce7aaca15d32c1284d85498a0f2bda7406b95'/>
<id>urn:sha1:732ce7aaca15d32c1284d85498a0f2bda7406b95</id>
<content type='text'>
Fix for protocol v2 support in "git fetch-pack" of shallow clones.

* jt/fetch-no-update-shallow-in-proto-v2:
  fetch-pack: respect --no-update-shallow in v2
  fetch-pack: call prepare_shallow_info only if v0
</content>
</entry>
<entry>
<title>Merge branch 'jt/fetch-pack-wanted-refs-optim'</title>
<updated>2019-04-25T07:41:16Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2019-04-25T07:41:16Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=abd7ccdd4ddcc2d2ce1d51943051c071902b159a'/>
<id>urn:sha1:abd7ccdd4ddcc2d2ce1d51943051c071902b159a</id>
<content type='text'>
Performance fix around "git fetch" that grabs many refs.

* jt/fetch-pack-wanted-refs-optim:
  fetch-pack: binary search when storing wanted-refs
</content>
</entry>
</feed>
