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

Re: [PATCH] fix many comment typos

From
HWHilco Wijbenga <hilco.wijbenga@gmail.com>
Date
Jun 3, 2012, 02:39 UTC
Message-ID
<CAE1pOi0sq-+1gAK1wrnjNqNY3bWGGAHDeW6879mdh4wLUbX_Og@mail.gmail.com>
In-Reply-To
<7vipf9z0gz.fsf@alter.siamese.dyndns.org>
On 2 June 2012 17:46, Junio C Hamano <gitster@pobox.com> wrote:
Show 39 quoted lines
> Hilco Wijbenga <hilco.wijbenga@gmail.com> writes:
>
>> On 2 June 2012 16:01, Junio C Hamano <gitster@pobox.com> wrote:
>>> Jim Meyering <jim@meyering.net> writes:
>>>
>>>> Use http://github.com/lyda/misspell-check to identify many typos.
>>>> Culprits identified and fixed automatically using these commands,
>>>> converting diagnostics to single-quote-safe sed -i commands:
>>>>
>>>> git ls-files|misspellings -f -|perl -nl \
>>>>   -e '/^(.*?)\[(\d+)\]: (\w+) -> "(.*?)"$/ or next;' \
>>>>   -e '($file,$n,$l,$r)=($1,$2,$3,$4); $q="'\''"; $r=~s/$q/$q\\$q$q/g;'\
>>>>   -e 'print "sed -i $q${n}s!$l!$r!$q $file"' \
>>>>  | grep -vE '\.po$|pt_BR' > k
>>>>
>>>> Filter out s/seeked/sought/ false positives (they relate to cg-seek):
>>>>   grep -vE 'seeked' k > j && mv j k
>>>
>>> ??
>>>> diff --git a/Documentation/RelNotes/1.5.4.4.txt b/Documentation/RelNotes/1.5.4.4.txt
>>>> index 323c1a8..83453db 100644
>>>> --- a/Documentation/RelNotes/1.5.4.4.txt
>>>> +++ b/Documentation/RelNotes/1.5.4.4.txt
>>>> @@ -21,7 +21,7 @@ Fixes since v1.5.4.3
>>>>
>>>>   * "git send-email" in 1.5.4.3 issued a bogus empty In-Reply-To: header.
>>>>
>>>> - * "git bisect" showed mysterious "won't bisect on seeked tree" error message.
>>>> + * "git bisect" showed mysterious "won't bisect on sought tree" error message.
>>>
>>> ??
>>
>> http://en.wiktionary.org/wiki/seeked
>
> Here is an advice to Hilco.  *THINK*
>
> I hate people who try to be clever by just quoting without saying
> anything, especially when it is very clear they didn't think the
> issue.  It is irritating.
Ouch.

You highlighted two changes that were both about "seeked". Your comment just said "??". I can think but I can't read your mind. :-)

Show 13 quoted lines
> That description in the 1.5.4.4 release note is stating a HISTORICAL
> FACT that the command in 1.5.4.3 gave that exact message.  What's
> the point of changing it in the name of typofix?  It is irrelevant
> if the word was misspelled; the whole point of the entry is report
> what was the problem the release fixed.
>
> What was strange to me, which is why I marked these two places with
> "??", is that Jim specifically filtered out false "seeked" positives
> in his procedure, but still the above somehow slipped in.
>
> That discouraged me from applying the patch, as it means I have to
> eyeball the whole thing to make sure that there aren't similar
> unintended changes.

That makes a lot of sense. My apologies for irritating you, that certainly wasn't my intention.

Previous: Junio C HamanoNext: Jim Meyering
Message 5 of 10 in “fix many comment typos”
  1. fix many comment typosJim Meyering, Jun 2, 2012
  2. Junio C HamanoJun 2, 2012
  3. Hilco WijbengaJun 2, 2012
  4. Junio C HamanoJun 3, 2012
  5. Hilco WijbengaJun 3, 2012
  6. Jim MeyeringJun 3, 2012
  7. René ScharfeJun 3, 2012
  8. Jim MeyeringJun 3, 2012
  9. Junio C HamanoJun 3, 2012
  10. Junio C HamanoJun 3, 2012

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.