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

Re: [PATCH 1/2] revert: refactor code that prints success or failure message

From
Christian Couder <chriscool@tuxfamily.org>
Date
Jul 13, 2010, 21:16 UTC
Message-ID
<201007132316.48645.chriscool@tuxfamily.org>
In-Reply-To
<20100712182733.GD17630@debian>
Hi Ram,
On Monday 12 July 2010 20:27:33 Ramkumar Ramachandra wrote:
Show 10 quoted lines
> Hi Christian,
> 
> Christian Couder writes:
> > This patch refactors the code that prints a message like
> > "Automatic cherry-pick failed. <help message>". This code was
> 
> [...]
> 
> This is good stuff. Can we expect the git-rebase--interactive.sh to be
> refactored to use the "cherry pick a range" feature in future?

I am trying to improve cherry-pick step by step so that hopefully in the end we have some sequencer like functionalities. So yes, I hope that it will be possible to refactor git-rebase--interactive.sh and perhaps other such shell scripts.

Thanks, Christian.

Previous: Ramkumar Ramachandra
Message 7 of 7 in “revert: refactor code that prints success or failure message”
  1. 1/2 revert: refactor code that prints success or failure messageChristian Couder, Jul 12, 2010
  2. Jonathan NiederJul 12, 2010
  3. Christian CouderJul 13, 2010
  4. Jonathan NiederJul 13, 2010
  5. Christian CouderJul 15, 2010
  6. Ramkumar RamachandraJul 12, 2010
  7. Christian CouderJul 13, 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.