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

Re: RFC: git bisect should accept "paths-to-be-excluded"

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 17, 2013, 19:04 UTC
Message-ID
<xmqqpps7xoax.fsf@gitster.dls.corp.google.com>
In-Reply-To
<1496b663-6b6c-45a2-95d1-cbe634b0d160@email.android.com>
Piotr Krukowiecki <piotr.krukowiecki@gmail.com> writes:
>  What about simply iterating over options in order in which they
>  are specified and the last option that matches specifies the
>  result?

But isn't it very inconsistent from the way normal pathspec works? "git log -- A B" and "git log -- B A" would give the same result.

Previous: Piotr KrukowieckiNext: Piotr Krukowiecki
Message 8 of 16 in “RFC: git bisect should accept "paths-to-be-excluded"”
  1. Toralf FörsterSep 16, 2013
  2. Christian CouderSep 17, 2013
  3. Matthieu MoySep 17, 2013
  4. Christian CouderSep 17, 2013
  5. Duy NguyenSep 17, 2013
  6. Junio C HamanoSep 17, 2013
  7. Piotr KrukowieckiSep 17, 2013
  8. Junio C HamanoSep 17, 2013
  9. Piotr KrukowieckiSep 17, 2013
  10. Junio C HamanoSep 17, 2013
  11. Duy NguyenSep 18, 2013
  12. Support pathspec magic :(exclude) and its short form :-Nguyễn Thái Ngọc Duy, Nov 20, 2013
  13. Junio C HamanoNov 20, 2013
  14. Duy NguyenNov 21, 2013
  15. Junio C HamanoNov 21, 2013
  16. Toralf FörsterSep 17, 2013

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.