delta/git.git/Documentation/git-bisect.txt, branch sb/string-list-split-appends

Merge branch 'jc/em-dash-in-doc'

2015-10-29T20:59:16+00:00

AsciiDoc markup fixes.

* jc/em-dash-in-doc:
  Documentation: AsciiDoc spells em-dash as double-dashes, not triple

Merge branch 'xf/user-manual-markup'

2015-10-29T20:59:14+00:00

AsciiDoc markup fixes.

* xf/user-manual-markup:
  Documentation: match undefline with the text in old release notes
  Documentation: match underline with the text
  Documentation: fix header markup

Documentation: AsciiDoc spells em-dash as double-dashes, not triple

2015-10-22T20:02:33+00:00

Again, we do not usually process release notes with AsciiDoc, but it
is better to be consistent.

This incidentally reveals breakages left by an ancient 5e00439f
(Documentation: build html for all files in technical and howto,
2012-10-23).  The index-format documentation was originally written
to be read as straight text without formatting and when the commit
forced everything in Documentation/ to go through AsciiDoc, it did
not do any adjustment--hence the double-dashes will be seen in the
resulting text that is rendered as preformatted fixed-width without
converted into em-dashes.

Signed-off-by: Junio C Hamano

Documentation: match underline with the text

2015-10-22T17:16:12+00:00

Even though AsciiDoc is more lenient when deciding if an underline
is for the contents on the previous line to find section headers, we
should match the length of them for other formatters to help them.

Signed-off-by: Junio C Hamano

bisect: allow setting any user-specified in 'git bisect start'

2015-08-03T18:42:43+00:00

This allows a natural user-interface when looking for any change in the
code, not just regression. For example:

git bisect start --term-old fast --term-new slow
git bisect fast
git bisect slow
...

There were several proposed user-interfaces for this feature. This patch
implements it as options to 'git bisect start' for the following reasons:

* By construction, the terms will be valid for one and only one
  bisection.

* Unlike positional arguments, using named options avoid having to
  remember an order.

* We can combine user-defined terms and passing old/new commits as
  argument to "git bisect start".

* The implementation is relatively simple.

See previous discussions:

  http://mid.gmane.org/1435337896-20709-3-git-send-email-Matthieu.Moy@imag.fr

Signed-off-by: Matthieu Moy 
Signed-off-by: Junio C Hamano

bisect: add 'git bisect terms' to view the current terms

2015-08-03T18:42:42+00:00

Signed-off-by: Matthieu Moy 
Signed-off-by: Junio C Hamano

bisect: add the terms old/new

2015-08-03T18:42:42+00:00

When not looking for a regression during a bisect but for a fix or a
change in another given property, it can be confusing to use 'good'
and 'bad'.

This patch introduce `git bisect new` and `git bisect old` as an
alternative to 'bad' and good': the commits which have a certain
property must be marked as `new` and the ones which do not as `old`.

The output will be the first commit after the change in the property.
During a new/old bisect session you cannot use bad/good commands and
vice-versa.

Some commands are still not available for old/new:
     * git rev-list --bisect does not treat the revs/bisect/new and
       revs/bisect/old-SHA1 files.

Old discussions:
	- http://thread.gmane.org/gmane.comp.version-control.git/86063
		introduced bisect fix unfixed to find fix.
	- http://thread.gmane.org/gmane.comp.version-control.git/182398
		discussion around bisect yes/no or old/new.
	- http://thread.gmane.org/gmane.comp.version-control.git/199758
		last discussion and reviews
New discussions:
	- http://thread.gmane.org/gmane.comp.version-control.git/271320
		( v2 1/7-4/7 )
	- http://comments.gmane.org/gmane.comp.version-control.git/271343
		( v2 5/7-7/7 )

Signed-off-by: Antoine Delaite 
Signed-off-by: Louis Stuber 
Signed-off-by: Valentin Duperray 
Signed-off-by: Franck Jonas 
Signed-off-by: Lucien Kong 
Signed-off-by: Thomas Nguy 
Signed-off-by: Huynh Khoi Nguyen Nguyen 
Signed-off-by: Matthieu Moy 
Signed-off-by: Junio C Hamano

Documentation/bisect: revise overall content

2015-06-26T21:15:05+00:00

Thoroughly revise the "git bisect" manpage, including:

* Beef up the "Description" section.

* Make the first long example less specific to kernel development.

* De-emphasize implementation details in a couple of places.

* Add "(roughly N steps)" in the places where example output is shown.

* Properly markup code within the prose.

* Lots of wordsmithing.

Signed-off-by: Michael Haggerty 
Signed-off-by: Matthieu Moy 
Signed-off-by: Junio C Hamano

Documentation/bisect: move getting help section to the end

2015-06-26T18:10:54+00:00

Signed-off-by: Matthieu Moy 
Signed-off-by: Junio C Hamano

Documentation: use "command-line" when used as a compound adjective, and fix other minor grammatical issues

2014-05-21T20:57:10+00:00

Signed-off-by: Jason St. John 
Signed-off-by: Junio C Hamano