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

Re: [PATCH] tests: rename work-tree tests to *work-tree*

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 22, 2016, 17:57 UTC
Message-ID
<xmqqzius7hma.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<56CAE460.8010405@drmicha.warpmail.net>
Michael J Gruber <git@drmicha.warpmail.net> writes:
Show 5 quoted lines
>> That is rather unfortunate.  Most of them predate the "worktree"
>> subcommand, I think, and having to rename them merely because a
>> subcommand with a confusing name appeared sound somewhat backwards.
>
> The question is: What ist the way forward?

Probably many. Take this as-is is one, rename newer ones that are about worktree subcommand to "s/worktree/worktree-cmd/" would be another.

Show 7 quoted lines
> I was looking for a proper place for a "git worktree" test and got
> confused by the status quo. My suggestion is one way to help that
> confusion, but I'd be happy to learn other ways. "grep" is an answer, too.
>
> Maybe it's also time to admit that the numbering and naming scheme in t/
> don't scale and that we should rather support other means of navigating
> t/, such as standardizing a comment boiler plate in each test or such.

Yeah, test_description at the beginning of each test may have been a well meaning attempt, but it is not helping us very much.

> In fact, giving up on the numbering scheme would allow to regroup tests
> more easily because there would be no room constraint any more (within a
> fixed finite set of numbers).

I tend to agree that may be an easier way forward in the longer term.

Thanks.
Previous: Michael J Gruber
Message 4 of 4 in “tests: rename work-tree tests to *work-tree*”
  1. tests: rename work-tree tests to *work-tree*Michael J Gruber, Feb 20, 2016
  2. Junio C HamanoFeb 20, 2016
  3. Michael J GruberFeb 22, 2016
  4. Junio C HamanoFeb 22, 2016

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.