undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

RelNotes: clarify "bisect run unexecutable" tweak

Browse Source 
We do not have to guess how common the mistake the change targets is
when describing it.  Such an argument may be good while proposing a
change, but does not quite belong in the record of what has already
happened, i.e. a release note.

Helped-by: Taylor Blau <me@ttaylorr.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Junio C Hamano 2022-04-13 16:42:33 -07:00
parent 1ac7422e39
commit 26ff9be6e7
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Documentation/RelNotes/2.36.0.txt
View File

@ -46,10 +46,10 @@ UI, Workflows & Features
* "git branch" learned the "--recurse-submodules" option. * "git branch" learned the "--recurse-submodules" option.
* A not-so-common mistake is to write a script to feed "git bisect * A user can forget to make a script file executable before giving
run" without making it executable, in which case all tests will it to "git bisect run". In such a case, all tests will exit with
exit with 126 or 127 error codes, even on revisions that are marked 126 or 127 error codes, even on revisions that are marked as good.
as good. Try to recognize this situation and stop iteration early. Try to recognize this situation and stop iteration early.
* When "index-pack" dies due to incoming data exceeding the maximum * When "index-pack" dies due to incoming data exceeding the maximum
allowed input size, include the value of the limit in the error allowed input size, include the value of the limit in the error