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

Re: [PATCH 0/4] tests: use "git xyzzy" form

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 3, 2008, 20:45 UTC
Message-ID
<7vwsht9cw5.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<7v8wu9athn.fsf@gitster.siamese.dyndns.org>
Thanks.
I looked at the output from:
    $ git grep -e git-'[a-z]' t/t[0-8]???-*.sh t/t9001-*.sh

after applying these patches to the tip of ho/dashless topic, 7e44c93 ('git foo' program identifies itself without dash in die() messages, 2008-08-31) to review what you did not change are reasonable.

I won't quote the whole output from the above grep, but there are a few lines worth commenting on.

t/t5300-pack-object.sh:test_description='git-pack-object t/t5305-include-tag.sh:test_description='git-pack-object --include-tag'

These might want changing.

t/t5602-clone-remote-exec.sh: echo "localhost git-upload-pack '\''/path/to/repo'\''" >expected t/t5602-clone-remote-exec.sh: GIT_SSH=./not_ssh git clone -u /something/bin/git-upload-pack localhost:/path/to/repo junk t/t5602-clone-remote-exec.sh: echo "localhost /something/bin/git-upload-pack '\''/path/to/repo'\''" >expected

These we do want to keep in git-foo form

The remainder of the grep output looked all reasonable; they hit options like "--git-dir" and "is-inside-git-dir", and pathnames like "git-gui" and ".git/rebase-merge/git-rebase-todo".

Doing this _carefully_ (otherwise the result would be useless) must have been quite a lot of effort, and what was posted seems to have been done quite carefully.

The cross-checking I did with "grep" in this message does *not* catch if you converted something that shouldn't have been converted (e.g. changing the pathname ".git/rebase-merge/git-rebase-todo" to "git rebase-todo" would have been a disaster). It needs real eyeballing of the patches themselves to catch such an error, and we would need help from people.

Volunteers? Just please say "I'll go through patch [n/4] line by line" now to avoid duplicated work with others (more eyeballs looking at the same thing will catch more errors, but I do not think we have that many volunteers here), and then after you are done, come back with "They all are command invocations and conversion is correct" or with "This one is incorrect and should be kept."

Oh, also, there are many other t9XXX series of tests. Can somebody volunteer to do the same for the rest of them?

Puh-leeeeze?
Previous: Junio C HamanoNext: Jeff King
Message 4 of 7 in “tests: use "git xyzzy" form”
  1. 0/4 tests: use "git xyzzy" formNanako Shiraishi, Sep 3, 2008
  2. Andreas EricssonSep 3, 2008
  3. Junio C HamanoSep 3, 2008
  4. Junio C HamanoSep 3, 2008
  5. Jeff KingSep 3, 2008
  6. Jeff KingSep 3, 2008
  7. Junio C HamanoSep 3, 2008

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.