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

Re[2]: [PATCH 1/3] Fixes bug: git-diff: class methods are not detected in hunk headers for Pascal

From
Алексей Шумкин <zapped@mail.ru>
Date
Jan 5, 2011, 11:53 UTC
Message-ID
<4510264083.20110105145302@mail.ru>
In-Reply-To
<201101041813.45053.trast@student.ethz.ch>
Hello, Thomas

TR> But the last line very conspicuously already mentions 'class', so why TR> does it fail? Yes, As you already discovered that last line match for class/record definition but not for class methods.

I did as you said I changed commit message (also included "Acked-by:"). So should I re-submit patch to the maillist as a new one or as an answer to this thread?

TR> Zapped wrote:
>> Signed-off-by: Zapped <zapped@mail.ru>

TR> As Junio already said, please provide a real name for the sign-off. TR> But I also found the commit message and content confusing, probably TR> because I haven't programmed Pascal for 15 years.

TR> You said
TR>   Fixes bug: git-diff: class methods are not detected in hunk headers for Pascal
Show 6 quoted lines
>>  PATTERNS("pascal",
>> -      "^((procedure|function|constructor|destructor|interface|"
>> +      "^(((class[ \t]+)?(procedure|function)|constructor|destructor|interface|"
>>               "implementation|initialization|finalization)[ \t]*.*)$"
>>        "\n"
>>        "^(.*=[ \t]*(class|record).*)$",

TR> But the last line very conspicuously already mentions 'class', so why TR> does it fail?

TR> I had to look up a bit of Pascal syntax.  Google helped with
TR>   http://www.freepascal.org/docs-html/ref/ref.html

TR> which answers this. Also, as stated in SubmittingPatches, we TR> generally word the messages as stating the behaviour of the changed TR> version in the present tense. So a better commit message would be

TR>   userdiff: match Pascal class methods

TR> Class declarations were already covered by the second pattern, but TR> class methods have the 'class' keyword in front too. Account for TR> it.

TR>   Signed-off-by: Алексей Крезов <zapped@mail.ru>

TR> Ok, now I feel silly for only having a two-liner despite my TR> complaints.

TR> That being said, I have now verified that the patch is good, and, you TR> can include my

TR>   Acked-by: Thomas Rast <trast@student.ethz.ch>
TR> in a reroll if you fix the above.
Previous: Thomas RastNext: Thomas Rast
Message 18 of 20 in “Fixes bug: git-diff: class methods are not detected in hunk headers for Pascal”
  1. 1/3 Fixes bug: git-diff: class methods are not detected in hunk headers for PascalZapped, Dec 25, 2010
  2. 2/3 Fixes bug: git-svn: svn.pathnameencoding is not respected with dcommit/set-treeZapped, Dec 25, 2010
  3. Thomas RastJan 4, 2011
  4. Eric WongJan 4, 2011
  5. Alexey ShumkinFeb 3, 2011
  6. Re[2]: [PATCH 2/3] Fixes bug: git-svn: svn.pathnameencoding is not respected with dcommit/set-treeАлексей Шумкин, Jan 5, 2011
  7. 3/3 Fixes bug: GIT_PS1_SHOWDIRTYSTATE is no not respect diff.ignoreSubmodules config variableZapped, Dec 25, 2010
  8. Jens LehmannDec 25, 2010
  9. Johannes SchindelinDec 25, 2010
  10. Junio C HamanoDec 26, 2010
  11. Re[2]: [PATCH 3/3] Fixes bug: GIT_PS1_SHOWDIRTYSTATE is no not respect diff.ignoreSubmodules config variableАлексей Шумкин, Dec 26, 2010
  12. Jens LehmannDec 27, 2010
  13. Johannes SchindelinDec 27, 2010
  14. Casey DahlinDec 27, 2010
  15. Re[2]: [PATCH 3/3] Fixes bug: GIT_PS1_SHOWDIRTYSTATE is no not respect diff.ignoreSubmodules config variableАлексей Крезов, Dec 26, 2010
  16. Re[2]: [PATCH 3/3] Fixes bug: GIT_PS1_SHOWDIRTYSTATE is no not respect diff.ignoreSubmodules config variableАлексей Шумкин, Dec 28, 2010
  17. Thomas RastJan 4, 2011
  18. Re[2]: [PATCH 1/3] Fixes bug: git-diff: class methods are not detected in hunk headers for PascalАлексей Шумкин, Jan 5, 2011
  19. Thomas RastJan 5, 2011
  20. Thomas RastJan 5, 2011

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.