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

Re: FEATURE REQUEST: Cherry pick in not checked out branch

From
Sverre Rabbelier <srabbelier@gmail.com>
Date
Mar 15, 2010, 09:43 UTC
Message-ID
<fabb9a1e1003150243o21bab937y122ac61d65777d5f@mail.gmail.com>
In-Reply-To
<be8f531d1003150139p7cc99700m807ab21bddf8fbb@mail.gmail.com>
Heya,
On Mon, Mar 15, 2010 at 09:39, Maxim Treskin <zerthurd@gmail.com> wrote:
> git cherry-pick applies the change introduced by specified commit only
> to currently checked out branch. Why this requirement exists? Is it
> possible to apply changes to not checked out branch, like:
Because you need a working directory to resolve conflicts.
-- 
Cheers,

Sverre Rabbelier
Previous: Tim MazidNext: Tim Mazid
Message 3 of 6 in “FEATURE REQUEST: Cherry pick in not checked out branch”
  1. Maxim TreskinMar 15, 2010
  2. Tim MazidMar 15, 2010
  3. Sverre RabbelierMar 15, 2010
  4. Tim MazidMar 15, 2010
  5. Michael J GruberMar 15, 2010
  6. Johannes SchindelinMar 15, 2010

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.