<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/Documentation/technical, branch v1.7.3.4</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v1.7.3.4</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v1.7.3.4'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2010-11-16T17:50:25Z</updated>
<entry>
<title>document sigchain api</title>
<updated>2010-11-16T17:50:25Z</updated>
<author>
<name>Jeff King</name>
<email>peff@peff.net</email>
</author>
<published>2010-11-12T04:24:56Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=ed296fe88dc8790f25a3546f1688dd40f8cbf2d1'/>
<id>urn:sha1:ed296fe88dc8790f25a3546f1688dd40f8cbf2d1</id>
<content type='text'>
It's pretty straightforward, but a stripped-down example
never hurts. And we should make clear that it is explicitly
OK to use SIG_DFL and SIG_IGN.

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 'jn/doc-backslash'</title>
<updated>2010-09-03T16:43:42Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2010-09-03T16:43:42Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=c0808fe70870f513a4fc020ec23500b88f8b1018'/>
<id>urn:sha1:c0808fe70870f513a4fc020ec23500b88f8b1018</id>
<content type='text'>
* jn/doc-backslash:
  Documentation: remove stray backslash in show-branch discussion
  Documentation: remove stray backslashes from "Fighting regressions" article
  Documentation: do not convert ... operator to ellipses
  Documentation: avoid stray backslash in user manual
  Documentation: avoid stray backslashes in core tutorial
  Documentation: remove stray backslashes in rev-parse manual
  Documentation: remove backslash before ~ in fast-import manual
  Documentation: remove stray backslash from "git bundle" manual
  Documentation/technical: avoid stray backslash in parse-options API docs
  Documentation: remove backslashes in manpage synopses
  Documentation: clarify quoting in gitignore docs
  Documentation: clarify quoting in "git rm" example
  Documentation: add missing quotes to "git grep" examples
  Documentation: clarify quoting in "git add" example
  Documentation: unbreak regex in show-ref manual
  Documentation: quoting trouble in "git rm" discussion
  Documentation: tweak description of log.date
</content>
</entry>
<entry>
<title>Merge branch 'jn/merge-renormalize'</title>
<updated>2010-09-03T16:43:41Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2010-09-03T16:43:41Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=8aed4a5e38a2a4f31567e01ab2a73341e972c08a'/>
<id>urn:sha1:8aed4a5e38a2a4f31567e01ab2a73341e972c08a</id>
<content type='text'>
* jn/merge-renormalize:
  merge-recursive --renormalize
  rerere: never renormalize
  rerere: migrate to parse-options API
  t4200 (rerere): modernize style
  ll-merge: let caller decide whether to renormalize
  ll-merge: make flag easier to populate
  Documentation/technical: document ll_merge
  merge-trees: let caller decide whether to renormalize
  merge-trees: push choice to renormalize away from low level
  t6038 (merge.renormalize): check that it can be turned off
  t6038 (merge.renormalize): try checkout -m and cherry-pick
  t6038 (merge.renormalize): style nitpicks
  Don't expand CRLFs when normalizing text during merge
  Try normalizing files to avoid delete/modify conflicts when merging
  Avoid conflicts when merging branches with mixed normalization

Conflicts:
	builtin/rerere.c
	t/t4200-rerere.sh
</content>
</entry>
<entry>
<title>Documentation/technical: avoid stray backslash in parse-options API docs</title>
<updated>2010-08-20T21:16:22Z</updated>
<author>
<name>Jonathan Nieder</name>
<email>jrnieder@gmail.com</email>
</author>
<published>2010-08-20T10:32:36Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=6dcca4d0ea4fe9ee09c939eaa0898f5895e5100a'/>
<id>urn:sha1:6dcca4d0ea4fe9ee09c939eaa0898f5895e5100a</id>
<content type='text'>
Due to some unpleasant interaction between the `quote', 'italics',
and `monospace` rules, a certain paragraph ends up rendered like so:

	‘short` is a character for the short option
	  (e.g. &lt;tt&gt;'e\’&lt;/tt&gt; for &lt;tt&gt;-e&lt;/tt&gt;, use &lt;tt&gt;0&lt;/tt&gt; to omit),

Use the {apostrophe} to avoid this.

While at it, escape "-&gt;" strings: they are meant as a literal
two-character C operator, not a right-pointing arrow.

Reported-by: Frédéric Brière &lt;fbriere@fbriere.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>unpack_trees: group error messages by type</title>
<updated>2010-08-11T17:36:06Z</updated>
<author>
<name>Matthieu Moy</name>
<email>Matthieu.Moy@imag.fr</email>
</author>
<published>2010-08-11T08:38:07Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=e6c111b4c092c0dd24c541b9721f5bc04641dcb0'/>
<id>urn:sha1:e6c111b4c092c0dd24c541b9721f5bc04641dcb0</id>
<content type='text'>
When an error is encountered, it calls add_rejected_file() which either
- directly displays the error message and stops if in plumbing mode
  (i.e. if show_all_errors is not initialized at 1)
- or stores it so that it will be displayed at the end with display_error_msgs(),

Storing the files by error type permits to have a list of files for
which there is the same error instead of having a serie of almost
identical errors.

As each bind_overlap error combines a file and an old file, a list cannot be
done, therefore, theses errors are not stored but directly displayed.

Signed-off-by: Matthieu Moy &lt;Matthieu.Moy@imag.fr&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>ll-merge: make flag easier to populate</title>
<updated>2010-08-06T16:20:01Z</updated>
<author>
<name>Jonathan Nieder</name>
<email>jrnieder@gmail.com</email>
</author>
<published>2010-08-05T11:17:38Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=73cf7f713da4fc797e2393a9e490ad4ec9466c53'/>
<id>urn:sha1:73cf7f713da4fc797e2393a9e490ad4ec9466c53</id>
<content type='text'>
ll_merge() takes its options in a flag word, which has a few
advantages:

 - options flags can be cheaply passed around in registers, while
   an option struct passed by pointer cannot;

 - callers can easily pass 0 without trouble for no options,
   while an option struct passed by value would not allow that.

The downside is that code to populate and access the flag word can be
somewhat opaque.  Mitigate that with a few macros.

Cc: Avery Pennarun &lt;apenwarr@gmail.com&gt;
Cc: Bert Wesarg &lt;bert.wesarg@googlemail.com&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>Documentation/technical: document ll_merge</title>
<updated>2010-08-06T16:20:01Z</updated>
<author>
<name>Jonathan Nieder</name>
<email>jrnieder@gmail.com</email>
</author>
<published>2010-08-05T11:16:51Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=24d113ec11d9948cedee4ba4687d0775e36b65f9'/>
<id>urn:sha1:24d113ec11d9948cedee4ba4687d0775e36b65f9</id>
<content type='text'>
Cc: Junio C Hamano &lt;gitster@pobox.com&gt;
Cc: Avery Pennarun &lt;apenwarr@gmail.com&gt;
Cc: Bert Wesarg &lt;bert.wesarg@googlemail.com&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>Merge branch 'maint'</title>
<updated>2010-07-12T06:47:29Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2010-07-12T06:47:29Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=609eb9f7ff2af45d52ea90c0678a442d46aaa163'/>
<id>urn:sha1:609eb9f7ff2af45d52ea90c0678a442d46aaa163</id>
<content type='text'>
* maint:
  Documentation: Spelling fix in protocol-capabilities.txt
  checkout: accord documentation to what git does
  t0005: work around strange $? in ksh when program terminated by a signal
</content>
</entry>
<entry>
<title>Documentation: Spelling fix in protocol-capabilities.txt</title>
<updated>2010-07-10T00:36:28Z</updated>
<author>
<name>Fredrik Skolmli</name>
<email>fredrik@frsk.net</email>
</author>
<published>2010-07-10T00:00:01Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=5d1e34158a3023af48541bf1731d202849929a12'/>
<id>urn:sha1:5d1e34158a3023af48541bf1731d202849929a12</id>
<content type='text'>
Signed-off-by: Fredrik Skolmli &lt;fredrik@frsk.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'jp/string-list-api-cleanup'</title>
<updated>2010-06-30T18:55:38Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2010-06-30T18:55:38Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=a53deac89eb6c65cd953c730f33b86ac3f72d647'/>
<id>urn:sha1:a53deac89eb6c65cd953c730f33b86ac3f72d647</id>
<content type='text'>
* jp/string-list-api-cleanup:
  string_list: Fix argument order for string_list_append
  string_list: Fix argument order for string_list_lookup
  string_list: Fix argument order for string_list_insert_at_index
  string_list: Fix argument order for string_list_insert
  string_list: Fix argument order for for_each_string_list
  string_list: Fix argument order for print_string_list
</content>
</entry>
</feed>
