git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2] blame: report correct number of lines in progress when using ranges

From
Philip Oakley <philipoakley@iee.email>
Date
Apr 8, 2022, 08:03 UTC
Message-ID
<9920b355-9003-e7c7-77ab-3432651674e9@iee.email>
In-Reply-To
<xmqqsfqq1bx9.fsf@gitster.g>
On 06/04/2022 16:14, Junio C Hamano wrote:
Show 18 quoted lines
> Philip Oakley <philipoakley@iee.email> writes:
>
>> On 05/04/2022 08:34, Bagas Sanjaya wrote:
>>> On 05/04/22 01.21, Edmundo Carmona Antoranz wrote:
>>>> When using ranges, use their sizes as the limit for progress
>>>> instead of the size of the full file.
>>> The progress limit is defined by number of affected lines, right?
>> I'd also wondered about 'their', thinking it was 'the files', rather
>> than 'the ranges' [within those files].
>>
>> perhaps: s/their/range/
> I actually think that it is obvious that "their" refers to the
> ranges and not the file.  Between "the ranges" and "the file", only
> the former is plural that "their" could possibly refer to.  Also,
> "instead ... the full file" makes the sentence nonsensical if it
> referred to the "file"---"we must use the number of lines in the
> file, instead of the number of lines in the file" simply would not
> make much sense.

I'm on the 'context and guidelines' side of English comprehension, so it was all about files being blamed.

>
> But I do not object to being more explicit.

The core point though was that it can be misunderstood, thus avoiding the indirection, as you say, makes it more explicit for the reader.

>
>> "When using ranges, use the range sizes as the limit for progress' ..

-- Philip

Previous: Junio C HamanoNext: Junio C Hamano
Message 9 of 11 in “blame: report correct number of lines in progress when using ranges”
  1. blame: report correct number of lines in progress when using rangesEdmundo Carmona Antoranz, Apr 4, 2022
  2. Edmundo Carmona AntoranzApr 4, 2022
  3. Junio C HamanoApr 4, 2022
  4. Bagas SanjayaApr 5, 2022
  5. Ævar Arnfjörð BjarmasonApr 5, 2022
  6. Edmundo Carmona AntoranzApr 5, 2022
  7. Philip OakleyApr 5, 2022
  8. Junio C HamanoApr 6, 2022
  9. Philip OakleyApr 8, 2022
  10. Junio C HamanoApr 8, 2022
  11. Ævar Arnfjörð BjarmasonApr 5, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.