Re: [PATCH] git-revert is one of the most misunderstood command in git, help users out.

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Nov 6, 2007, 12:16 UTC
Message-ID: <Pine.LNX.4.64.0711061214520.4362@racer.site>
In-Reply-To: <47305536.5010308@viscovery.net>

Hi,

On Tue, 6 Nov 2007, Johannes Sixt wrote:

Show 5 quoted lines

> Junio C Hamano schrieb:
> > I am wondering what "git cherry-pick -- <paths>" should do.  My
> > current thinking is that it would not make any sense at all.
> 
> IMO, at least "git cherry-pick -n -- <paths>" makes tons of sense.

I guess you missed that Junio did not specify any commit. With a commit, I agree, it makes tons of sense.

Without a commit, it would default to... uhm... HEAD? And applying the changes to a given file, which are already in HEAD, no, that does not make sense.

Ciao, Dscho

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