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

Re: [PATCH] Deprecate git-cherry

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 6, 2007, 20:48 UTC
Message-ID
<7vmyy9dzrr.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.64.0707061722020.4093@racer.site>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 11 quoted lines
> A cleaner alternative was introduced in v1.5.2~185^2~1, which not only
> allows you to list the commits, but to inspect them, too:
>
> 	git log --cherry-pick <upstream>...[<head>]
>
> There is a functional difference, though: git cherry shows both 
> directions, <upstream>...<head> and <head>...<upstream>, and prefixes
> the commits with '+' and '-', respectively.
>
> 'git rev-list --cherry-pick <upstream>...[<head>]' only shows one 
> direction, and does not prefix the commits.
Eh, --left-right anybody?

git-cherry is used by people's scripts, and I do not think deprecating is an option at least in the short term.

Previous: Johannes SchindelinNext: Johannes Schindelin
Message 2 of 3 in “Deprecate git-cherry”
  1. Deprecate git-cherryJohannes Schindelin, Jul 6, 2007
  2. Junio C HamanoJul 6, 2007
  3. Johannes SchindelinJul 6, 2007

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.