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

Re: Triggering "BUG: wt-status.c:476: multiple renames on the same target? how?"

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Sep 27, 2018, 10:15 UTC
Message-ID
<CAPig+cRW1S78Oiq9RPZjOBC651DO3=8Uzg69sji+x1QpOeH4ig@mail.gmail.com>
In-Reply-To
<20180927072043.19130-1-newren@gmail.com>
On Thu, Sep 27, 2018 at 3:20 AM Elijah Newren <newren@gmail.com> wrote:
Show 17 quoted lines
> Subject: [PATCH] commit: fix erroneous BUG, 'multiple renames on the same
>  target? how?'
> [...]
> Signed-off-by: Elijah Newren <newren@gmail.com>
> ---
> diff --git a/t/t7500-commit.sh b/t/t7500-commit.sh
> @@ -359,4 +359,27 @@ test_expect_success 'new line found before status message in commit template' '
> +test_expect_success 'setup empty commit with unstaged rename and copy' '
> +       test_create_repo unstaged_rename_and_copy &&
> +       (
> +               cd unstaged_rename_and_copy &&
> +
> +               echo content >orig &&
> +               git add orig &&
> +               test_commit orig &&
> +
> +               cp -a orig new_copy &&
Non-portable -a option. Not in POSIX[1].
[1]: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/cp.html
> +               mv orig new_rename &&
> +               git add -N new_copy new_rename
> +       )
> +'
Previous: Elijah NewrenNext: Duy Nguyen
Message 2 of 4 in “Re: Triggering "BUG: wt-status.c:476: multiple renames on the same target? how?"”
  1. Elijah NewrenSep 27, 2018
  2. Eric SunshineSep 27, 2018
  3. Duy NguyenSep 27, 2018
  4. [PATCHv2] commit: fix erroneous BUG, 'multiple renames on the same target? how?'Elijah Newren, Sep 27, 2018

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.