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

Re: [BUG] cherry-pick ignores some arguments

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 15, 2012, 15:06 UTC
Message-ID
<7v62asd379.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20120615091425.20e40af9@chalon.bertin.fr>
Yann Dirson <dirson@bertin.fr> writes:
> Another orthogonal UI issue I see, is that rev-list could be more
> user-friendly to warn the user when one element of a rev list is
> ignored because of another one.

Sometimes my maint-1.7.8 branch may still have commits that are not in maint branch, sometimes maint-1.7.9 branch is a true subset of maint branch. "rev-list ^maint maint-1.7.8 maint-1.7.9" is a very sensible thing to ask to find out what is still not in 'maint' out of stuff that are _usually_ but not always part of 'maint'.

Complaining on such a query is not user-friendly at all.
Previous: Carlos Martín NietoNext: Junio C Hamano
Message 10 of 11 in “[BUG] cherry-pick ignores some arguments”
  1. Yann DirsonJun 14, 2012
  2. Carlos Martín NietoJun 14, 2012
  3. Yann DirsonJun 15, 2012
  4. Carlos Martín NietoJun 15, 2012
  5. 1/2 Documentation: --no-walk is no-op if range is specifiedCarlos Martín Nieto, Jun 15, 2012
  6. 2/2 git-cherry-pick.txt: make clearer when revision walking gets activatedCarlos Martín Nieto, Jun 15, 2012
  7. Junio C HamanoJun 15, 2012
  8. Junio C HamanoJun 15, 2012
  9. Carlos Martín NietoJun 15, 2012
  10. Junio C HamanoJun 15, 2012
  11. Junio C HamanoJun 15, 2012

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.