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

Re: [PATCH] clean: demonstrate a bug with pathspecs

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Jan 16, 2020, 00:03 UTC
Message-ID
<20200116000312.GD146834@google.com>
In-Reply-To
<pull.526.git.1579119946211.gitgitgadget@gmail.com>
Hi,
Derrick Stolee wrote:
Show 8 quoted lines
> b9660c1 (dir: fix checks on common prefix directory, 2019-12-19)
> modified the way pathspecs are handled when handling a directory
> during "git clean -f <path>". While this improved the behavior
> for known test breakages, it also regressed in how the clean
> command handles cleaning a specified file.
>
> Add a test case that demonstrates this behavior. This test passes
> before b9660c1 then fails after.

Can this commit message say a little more about the nature of the bug? For example, what kind of workflow does this come up in for end users?

[...]
>     While integrating v2.25.0 into the microsoft/git fork, one of our VFS
>     for Git functional tests started failing.

This is also useful information to put in the commit message: e.g. "Noticed via VFS for Git's functional test <test name>". It provides useful context when looking at such a patch later.

[...]
>                                      Elijah is CC'd in case he still has
>     context on this area.

Thanks and hope that helps, Jonathan

Previous: Derrick StoleeNext: Derrick Stolee
Message 4 of 9 in “clean: demonstrate a bug with pathspecs”
  1. clean: demonstrate a bug with pathspecsDerrick Stolee via GitGitGadget, Jan 15, 2020
  2. Kyle MeyerJan 15, 2020
  3. Derrick StoleeJan 16, 2020
  4. Jonathan NiederJan 16, 2020
  5. Derrick StoleeJan 16, 2020
  6. Elijah NewrenJan 16, 2020
  7. Derrick StoleeJan 16, 2020
  8. Elijah NewrenJan 16, 2020
  9. Junio C HamanoJan 16, 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.