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

Re: [PATCH] tree-walk.c: fix overoptimistic inclusion in :(exclude) matching

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Nov 4, 2018, 06:27 UTC
Message-ID
<CAPig+cQTaG=pTQ_fQp8gv-4+bzJrSGCy8zK_iDeJsFNeX+4Cpg@mail.gmail.com>
In-Reply-To
<CAPig+cS7b0nenb0+0jyXE=-bDkhapmYE8Yr6VfyAWRq3ydjPOg@mail.gmail.com>
On Sat, Nov 3, 2018 at 8:25 PM Eric Sunshine <sunshine@sunshineco.com> wrote:
Show 15 quoted lines
> On Sat, Nov 3, 2018 at 11:31 AM Nguyễn Thái Ngọc Duy <pclouds@gmail.com> wrote:
> > +test_expect_success 't_e_i() exclude case #8' '
> > +       git init case8 &&
> > +       (
> > +               cd case8 &&
> > +               echo file >file1 &&
> > +               echo file >file2 &&
> > +               git add . &&
>
> Won't this loose git-add invocation end up adding all the junk files
> from earlier tests? One might have expected to see the more restricted
> invocation:
>     git add file1 file2 &&
> to make it easier to reason about the test and not worry about someone
> later inserting tests above this one which might interfere with it.

Upon reflection, there shouldn't be any junk files since this test is creating a new repository and "file1" and "file2" are the only files present. Apparently, I wasn't paying close enough attention when I made the earlier observation.

Anyhow, the more restricted git-add invocation you used in the re-roll is still preferable since it makes the intention obvious. Thanks.

Previous: Eric SunshineNext: Duy Nguyen
Message 7 of 10 in “Re: bug?: git grep HEAD with exclude in pathspec not taken into account”
  1. Christophe BliardOct 24, 2018
  2. Duy NguyenOct 24, 2018
  3. Christophe BliardOct 24, 2018
  4. Duy NguyenOct 27, 2018
  5. tree-walk.c: fix overoptimistic inclusion in :(exclude) matchingNguyễn Thái Ngọc Duy, Nov 3, 2018
  6. Eric SunshineNov 4, 2018
  7. Eric SunshineNov 4, 2018
  8. Duy NguyenNov 4, 2018
  9. tree-walk.c: fix overoptimistic inclusion in :(exclude) matchingNguyễn Thái Ngọc Duy, Nov 4, 2018
  10. Junio C HamanoNov 5, 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.