Re: [PATCH 7/8] Documentation/cherry-pick: describe passing more than one commit

From: Jonathan Nieder <jrnieder@gmail.com>
Date: Jun 2, 2010, 06:14 UTC
Message-ID: <20100602061452.GA9439@progeny.tock>
In-Reply-To: <201006020757.34186.chriscool@tuxfamily.org>

Christian Couder wrote:

> On Tuesday 01 June 2010 11:51:24 Jonathan Nieder wrote:

Show 9 quoted lines

>> git rev-list master -- README | git cherry-pick -n --stdin::
>> 
>> 	Apply the changes introduced by all commits on the master
>> 	branch that touched README to the working tree and index,
>> 	so the result can be inspected and made into a single new
>> 	commit if suitable.
>
> I think "--reverse" is needed after "rev-list" and cherry-pick has no --stdin 
> option.

That’s too bad. :(  git show inherits it from rev-list.

Your new series looks good. Maybe I will obfuscate the examples some other day.

Thanks, Jonathan

$ 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.