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

Re: Unexpected cherry-pick behaviour

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 14, 2013, 19:39 UTC
Message-ID
<7vmwk3gr39.fsf@alter.siamese.dyndns.org>
In-Reply-To
<3FFF08967D2E480FA6B0E0EE3A72A8D9@PhilipOakley>
"Philip Oakley" <philipoakley@iee.org> writes:
> Would this be a good use of the
>    * Magic pathspecs like ":(icase)
> that was recently released (v1.8.5  2Dec13)  so that the merge stages
> can be named.

Because the pathspec mechahism is for you to tell an operation that works on a collection of paths (e.g. "all the paths in the HEAD", "all the paths at stage #1 in the index") to narrow the set it operates on down to only those that match, I do not think it is a good match at all to what you are trying to do.

Previous: Philip OakleyNext: Philip Oakley
Message 8 of 13 in “Unexpected cherry-pick behaviour”
  1. Paulo MatosDec 10, 2013
  2. Junio C HamanoDec 10, 2013
  3. Paulo MatosDec 11, 2013
  4. Antoine PelisseDec 11, 2013
  5. Paulo MatosDec 11, 2013
  6. Antoine PelisseDec 14, 2013
  7. Philip OakleyDec 14, 2013
  8. Junio C HamanoDec 14, 2013
  9. Philip OakleyDec 15, 2013
  10. Philip OakleyDec 16, 2013
  11. Junio C HamanoDec 16, 2013
  12. Junio C HamanoDec 14, 2013
  13. Antoine PelisseDec 14, 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.