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

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

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Mar 15, 2010, 11:01 UTC
Message-ID
<4B9E13A4.3090502@drmicha.warpmail.net>
In-Reply-To
<SNT124-W1769013489F8B7CE42C581C42E0@phx.gbl>
Tim Mazid venit, vidit, dixit 15.03.2010 10:54:
> 
> Hi,
>  
> Could we not make cherry-pick "stash, checkout, cherry-pick, checkout, pop"?
Sure, that would be 5 command invocations requiring a work tree ;)

Seriously, you can make this into an alias or custom commend, of course, but it would possibly need to stop in a state of conflict, the very same way that rebase -i may. There are structural improvements on the way which will make rebase -i, cherry-pick and so on use the same underlying code base, and that will help implementing requests such as this one.

Michael

P.S.: Please don't top-post (I cut it). P.P.S.: Please don't cull cc (I re-added SR).

Previous: Tim MazidNext: Johannes Schindelin
Message 5 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.