From: Kristoffer Haugsbakk Date: Fri, 16 Jan 2026 13:34:49 GMT Subject: Re: [PATCH v2 0/5] Change git-last-modified(1) default behavior and add documentation Message-ID: <72aabd0f-bafa-4013-99b7-f065e8977f8c@app.fastmail.com> In-Reply-To: <20260116-toon-last-modified-zzzz-v2-0-79e44f2806fe@iotcl.com> On Fri, Jan 16, 2026, at 14:22, Toon Claes wrote: > We have had several reports[1][2] from users that have been thoroughly > confused by the default behaviour of git-last-modified(1). Most > importantly, when using the command on trees other than the root tree > the requests are seemingly ignoring that request and instead blame the > top-level subtree. For example: > > $ git last-modified t/lib-bash.sh > acdfea4394db8e8b42f48e36f7726d64a909a89d t > > This result is completely unexpected and feels buggy to anybody who is > not deeply familiar with git-last-modified(1). Furthermore, users > typically have a hard time to figure out the correct parameters. > > This series changes the behavior to something that intuitively makes > more sense. > > The change of the default behavior is done in the last commit, in the > lead-up commits changes in the documentation are made. > > [1]: > [2]: <03f96860-29fc-42a7-a220-c3ec65eb8516@codeberg.org> > > --- > Changes in v2: > - Change the default --max-depth. > - Split up commits in smaller pieces. > - Add more testss > - Link to v1: > https://patch.msgid.link/20251126-toon-last-modified-zzzz-v1-0-608350df0caa@iotcl.com > > Cc: "Kristoffer Haugsbakk" > Cc: Gusted I think the Cc list got mixed up. > > --- >[snip]