grep output revisions

[Steve Borho]

On Fri, Aug 21, 2009 at 7:49 AM, TK Soh<teekaysoh at gmail.com> wrote:
> On Fri, Aug 21, 2009 at 9:42 AM, Abderrahim Kitouni<a.kitouni at gmail.com> wrote:
>> Hi,
>>
>> 2009/8/21 TK Soh <teekaysoh at gmail.com>:
>>> I am trying to understand the revisions captured by hg grep:
>> [...]
>>>
>>> I found this in the help text, but I am not sure how to interpret it:
>>>
>>>    By default, grep only prints output for the first revision of a
>>>    file in which it finds a match. To get it to print every revision
>>>    that contains a change in match status ("-" for a match that
>>>    becomes a non-match, or "+" for a non-match that becomes a match),
>>>    use the --all flag.
>>>
>>
>> If I understrand correctly, without --all, grep prints the latest
>> revision containing the match (that is, the changeset of the latest
>> revision of the file).
>
> The strange thing is that rev 8810 is the last change on these line
> (per annotate), which grep should have reported. How on earth would it
> end up in rev 9331?

Without --all, grep looks at the entire file contents and not just changed
lines.  I'm not sure I understand why, but that's what it does.

--
Steve Borho