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

Re: [BUG] cherry-pick ignores some arguments

From
Carlos Martín Nieto <cmn@elego.de>
Date
Jun 15, 2012, 14:39 UTC
Message-ID
<1339771158.4625.59.camel@beez.lab.cmartin.tk>
In-Reply-To
<1339765943.4625.57.camel@beez.lab.cmartin.tk>
On Fri, 2012-06-15 at 15:12 +0200, Carlos Martín Nieto wrote:
> The typical cherry-pick usage is for a few select commits out of a
> different branch. The manpage itself only started explaining the ranges
> in 2010 and they may be more of a side-effect than a conscious design
> decision. But that's neither here nor there.

Disregard this part. I just found the patches. For some reason I thought that the capability was there much earlier.

   cmn
Previous: Junio C HamanoNext: Junio C Hamano
Message 9 of 11 in “[BUG] cherry-pick ignores some arguments”
  1. Yann DirsonJun 14, 2012
  2. Carlos Martín NietoJun 14, 2012
  3. Yann DirsonJun 15, 2012
  4. Carlos Martín NietoJun 15, 2012
  5. 1/2 Documentation: --no-walk is no-op if range is specifiedCarlos Martín Nieto, Jun 15, 2012
  6. 2/2 git-cherry-pick.txt: make clearer when revision walking gets activatedCarlos Martín Nieto, Jun 15, 2012
  7. Junio C HamanoJun 15, 2012
  8. Junio C HamanoJun 15, 2012
  9. Carlos Martín NietoJun 15, 2012
  10. Junio C HamanoJun 15, 2012
  11. Junio C HamanoJun 15, 2012

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.