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

Re: [PATCH 2/4] t6423: more involved directory rename test

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Oct 15, 2020, 20:57 UTC
Message-ID
<CAPig+cQ=WjqfN68GcpaJBC4zjP_q2KnY9k15ErWkFM08TyCVjA@mail.gmail.com>
In-Reply-To
<c9637d70caed8a265096fa701833eca3ed52d0f3.1602794791.git.gitgitgadget@gmail.com>

On Thu, Oct 15, 2020 at 4:46 PM Elijah Newren via GitGitGadget <gitgitgadget@gmail.com> wrote:

> Add a new testcase modelled on a real world repository example that
> served multiple purposes:

A couple minor style nits I noticed while quickly running my eye over the patch...

> +               for i in `test_seq 1 88`; do
> +                       echo content $i >dir/unchanged/file_$i
> +               done &&
'do' on its own line, and prefer $(...) over `...`:
    for i in $(test_seq 1 88)
    do
        echo content $i >dir/unchanged/file_$i
    done &&
(Not necessarily worth a re-roll, though.)
Previous: Elijah Newren via GitGitGadget
Message 6 of 6 in “Directory rename detection testcases and rules”
  1. 0/4 Directory rename detection testcases and rulesElijah Newren via GitGitGadget, Oct 15, 2020
  2. 3/4 t6423: update directory rename detection tests with new ruleElijah Newren via GitGitGadget, Oct 15, 2020
  3. 4/4 t6423: more involved rules for renaming directories into each otherElijah Newren via GitGitGadget, Oct 15, 2020
  4. 1/4 directory-rename-detection.txt: update references to regression testsElijah Newren via GitGitGadget, Oct 15, 2020
  5. 2/4 t6423: more involved directory rename testElijah Newren via GitGitGadget, Oct 15, 2020
  6. Eric SunshineOct 15, 2020

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.