Junio C Hamano writes:
> "Robert P. J. Day" writes:
>
>> in this sense, i don't think "indicate" and "identify" are
>> completely interchangeable. in my mind, the word "identify" does
>> nothing more than, you know, point at something and say, "that one,
>> that's the one i'm talking about;" i
"Robert P. J. Day" writes:
> in this sense, i don't think "indicate" and "identify" are
> completely interchangeable. in my mind, the word "identify" does
> nothing more than, you know, point at something and say, "that one,
> that's the one i'm talking about;" it goes no further than that.
>
>
On Fri, 24 Nov 2017, Junio C Hamano wrote:
> "Robert P. J. Day" writes:
... snip ...
> > -to indicate that it was after.
> > +to indicate a single commit after that change.
>
> As to "identify", I would say it is better to consistently use
> "indicate" like the original of these two hunks at th
"Robert P. J. Day" writes:
> This command uses a binary search algorithm to find which commit in
> -your project's history introduced a bug. You use it by first telling
> -it a "bad" commit that is known to contain the bug, and a "good"
> -commit that is known to be before the bug was introduced
Reword the man page for "git bisect" to emphasize that, in the general
case, this command can take more than one good commit to define the
initial range of commits to examine.
Signed-off-by: Robert P. J. Day
---
diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt
index 4a14
5 matches
Mail list logo
