git/Documentation, branch v2.9.3Mirror of https://git.kernel.org/pub/scm/git/git.git/
https://git.shady.money/git/atom?h=v2.9.32016-08-12T16:17:51ZGit 2.9.32016-08-12T16:17:51ZJunio C Hamanogitster@pobox.com2016-08-12T16:17:51Zurn:sha1:e0c1ceafc5bece92d35773a75fff59497e1d9bd5
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Yet another batch for 2.9.32016-08-10T18:56:56ZJunio C Hamanogitster@pobox.com2016-08-10T18:56:56Zurn:sha1:8e4b75a97beaf88aa83ab2b18c07bd8ae4954f28
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Merge branch 'jh/clean-smudge-f-doc' into maint2016-08-10T18:55:34ZJunio C Hamanogitster@pobox.com2016-08-10T18:55:34Zurn:sha1:019d8a409f6ff077c171589e89ac84f6575da86c
A minor documentation update.
This was split out from a stalled jh/clean-smudge-annex topic
before discarding it.
* jh/clean-smudge-f-doc:
clarify %f documentation
Merge branch 'jc/hashmap-doc-init' into maint2016-08-10T18:55:31ZJunio C Hamanogitster@pobox.com2016-08-10T18:55:31Zurn:sha1:33481c1e59fa557553052912a005094aaf913074
The API documentation for hashmap was unclear if hashmap_entry
can be safely discarded without any other consideration. State
that it is safe to do so.
* jc/hashmap-doc-init:
hashmap: clarify that hashmap_entry can safely be discarded
Hopefully final batch for 2.9.32016-08-08T21:22:36ZJunio C Hamanogitster@pobox.com2016-08-08T21:22:36Zurn:sha1:00f27feb6afaa9e5f91a0852a5a20c041ba0a421
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Merge branch 'sb/pack-protocol-doc-nak' into maint2016-08-08T21:21:47ZJunio C Hamanogitster@pobox.com2016-08-08T21:21:47Zurn:sha1:593be730f21a10b14368464180d1e6f3402b8c4a
A doc update.
* sb/pack-protocol-doc-nak:
Documentation: pack-protocol correct NAK response
Merge branch 'jc/doc-diff-filter-exclude' into maint2016-08-08T21:21:44ZJunio C Hamanogitster@pobox.com2016-08-08T21:21:44Zurn:sha1:2f8c654edb0c8805749c60228ad9abb5984fba63
Belated doc update for a feature added in v1.8.5.
* jc/doc-diff-filter-exclude:
diff: document diff-filter exclusion
clarify %f documentation2016-08-03T17:10:35ZJoey Hessjoeyh@joeyh.name2016-07-11T22:45:05Zurn:sha1:52db4b0467f157230d2746f10435d070ad859bae
It's natural to expect %f to be an actual file on disk; help avoid that
mistake.
Signed-off-by: Joey Hess <joeyh@joeyh.name>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
hashmap: clarify that hashmap_entry can safely be discarded2016-08-02T21:34:17ZJunio C Hamanogitster@pobox.com2016-08-02T18:04:05Zurn:sha1:54ba5a1a16c0306bda1c304a341b9e4e7ab44684
The API documentation said that the hashmap_entry structure to be
embedded in the caller's structure is to be treated as opaque, which
left the reader wondering if it can safely be discarded when it no
longer is necessary. If the hashmap_entry structure had references
to external resources such as allocated memory or an open file
descriptor, merely free(3)ing the containing structure (when the
caller's structure is on the heap) or letting it go out of scope
(when it is on the stack) would end up leaking the external
resource.
Document that there is no need for hashmap_entry_clear() that
corresponds to hashmap_entry_init() to give the API users a little
bit of peace of mind.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Some fixes for 2.9.32016-07-28T18:28:32ZJunio C Hamanogitster@pobox.com2016-07-28T18:28:32Zurn:sha1:08df31eeccfe1576971ea4ba42570a424c3cfc41
Signed-off-by: Junio C Hamano <gitster@pobox.com>