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

Re: [PATCH v2 1/3] last-modified: rewrite error message when more than one revision given

From
Toon Claes <toon@iotcl.com>
Date
Jan 15, 2026, 11:33 UTC
Message-ID
<87jyxjjejz.fsf@iotcl.com>
In-Reply-To
<aWd2SLrBQRBC1e2S@pks.im>
Patrick Steinhardt <ps@pks.im> writes:
Show 16 quoted lines
> On Wed, Jan 14, 2026 at 11:24:45AM +0100, Toon Claes wrote:
>> diff --git a/builtin/last-modified.c b/builtin/last-modified.c
>> index c80f0535f6..06e3f79aec 100644
>> --- a/builtin/last-modified.c
>> +++ b/builtin/last-modified.c
>> @@ -145,16 +145,20 @@ static int populate_paths_from_revs(struct last_modified *lm)
>>  		if (obj->item->flags & UNINTERESTING)
>>  			continue;
>>  
>> -		if (num_interesting++)
>> -			return error(_("last-modified can only operate on one tree at a time"));
>> +		if (num_interesting++) {
>> +			ret = error(_("last-modified can only operate on one revision at a time"));
>
> Do we maybe want to be a bit more specific and say committish instead of
> revision?

I was thinking about mentioning something like "commit-ish" instead, but I felt "commit-ish" isn't a commonly used term toward end-users. Looking at gitglossary(7), it says "revision" is a "synonym for commit". I'm happy to change this message, but I'm not sure s/revision/commit-ish/ is the best change for this.

Show 12 quoted lines
>> diff --git a/t/t8020-last-modified.sh b/t/t8020-last-modified.sh
>> index 50f4312f71..1183ae667b 100755
>> --- a/t/t8020-last-modified.sh
>> +++ b/t/t8020-last-modified.sh
>> @@ -12,7 +12,7 @@ test_expect_success 'setup' '
>>  	test_commit 3 a/b/file
>>  '
>>  
>> -test_expect_success 'cannot run last-modified on two trees' '
>> +test_expect_success 'cannot run last-modified on two revision' '
>
> Nit: s/revision/revisions/
Thanks.
Show 6 quoted lines
>>  	test_must_fail git last-modified HEAD HEAD~1
>
> Another tiny nit: I'm always a bit wary around tests that don't verify
> the reason for failure. We might want to add:
>
>     test_grep "last-modified can only operate on one revision at a time" err
Okay, I'll rework this one and the one adding in the other commit.
-- 
Cheers,
Toon
Previous: Patrick SteinhardtNext: Patrick Steinhardt
Message 7 of 55 in “last-modified: verify revision argument is a commit-ish”
  1. last-modified: verify revision argument is a commit-ishToon Claes, Jan 12, 2026
  2. Junio C HamanoJan 12, 2026
  3. Patrick SteinhardtJan 13, 2026
  4. 0/3 Fix git-last-modified(1) bug triggered when passing a tree-ishToon Claes, Jan 14, 2026
  5. 1/3 last-modified: rewrite error message when more than one revision givenToon Claes, Jan 14, 2026
  6. Patrick SteinhardtJan 14, 2026
  7. Toon ClaesJan 15, 2026
  8. Patrick SteinhardtJan 15, 2026
  9. Kristoffer HaugsbakkJan 15, 2026
  10. Patrick SteinhardtJan 16, 2026
  11. Toon ClaesJan 16, 2026
  12. Junio C HamanoJan 16, 2026
  13. Patrick SteinhardtJan 19, 2026
  14. Kristoffer HaugsbakkJan 25, 2026
  15. Kristoffer HaugsbakkJan 15, 2026
  16. 2/3 last-modified: remove double error messageToon Claes, Jan 14, 2026
  17. Patrick SteinhardtJan 14, 2026
  18. 3/3 last-modified: verify revision argument is a commit-ishToon Claes, Jan 14, 2026
  19. Patrick SteinhardtJan 14, 2026
  20. Kristoffer HaugsbakkJan 15, 2026
  21. Junio C HamanoJan 15, 2026
  22. Toon ClaesJan 16, 2026
  23. 0/4 Fix git-last-modified(1) bug triggered when passing a tree-ishToon Claes, Jan 16, 2026
  24. 1/4 last-modified: rewrite error message when more than one revision givenToon Claes, Jan 16, 2026
  25. Junio C HamanoJan 16, 2026
  26. 2/4 last-modified: fix memory leak when more than one revision is givenToon Claes, Jan 16, 2026
  27. 3/4 last-modified: remove double error messageToon Claes, Jan 16, 2026
  28. Junio C HamanoJan 16, 2026
  29. 4/4 last-modified: verify revision argument is a commit-ishToon Claes, Jan 16, 2026
  30. Junio C HamanoJan 16, 2026
  31. 0/4 Fix git-last-modified(1) bug triggered when passing a tree-ishToon Claes, Jan 23, 2026
  32. 1/4 last-modified: rewrite error message when more than one revision givenToon Claes, Jan 23, 2026
  33. Junio C HamanoJan 23, 2026
  34. 2/4 last-modified: fix memory leak when more than one revision is givenToon Claes, Jan 23, 2026
  35. Junio C HamanoJan 23, 2026
  36. 3/4 last-modified: remove double error messageToon Claes, Jan 23, 2026
  37. Junio C HamanoJan 23, 2026
  38. 4/4 last-modified: verify revision argument is a commit-ishToon Claes, Jan 23, 2026
  39. Junio C HamanoJan 23, 2026
  40. Junio C HamanoJan 23, 2026
  41. 0/4 Fix git-last-modified(1) bug triggered when passing a tree-ishToon Claes, Jan 27, 2026
  42. 1/4 last-modified: rewrite error message when more than one commit givenToon Claes, Jan 27, 2026
  43. 2/4 last-modified: fix memory leak when more than one commit is givenToon Claes, Jan 27, 2026
  44. 3/4 last-modified: remove double error messageToon Claes, Jan 27, 2026
  45. 4/4 last-modified: verify revision argument is a commit-ishToon Claes, Jan 27, 2026
  46. Junio C HamanoJan 27, 2026
  47. Toon ClaesJan 29, 2026
  48. 0/4 Fix git-last-modified(1) bug triggered when passing a tree-ishToon Claes, Jan 30, 2026
  49. 1/4 last-modified: rewrite error message when more than one commit givenToon Claes, Jan 30, 2026
  50. 2/4 last-modified: fix memory leak when more than one commit is givenToon Claes, Jan 30, 2026
  51. 3/4 last-modified: remove double error messageToon Claes, Jan 30, 2026
  52. 4/4 last-modified: verify revision argument is a commit-ishToon Claes, Jan 30, 2026
  53. Patrick SteinhardtFeb 6, 2026
  54. Junio C HamanoJan 30, 2026
  55. Patrick SteinhardtFeb 6, 2026

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.