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

Re: git cherry not marking commits with equivalent upstream

From
APAndrew Pimlott <andrew@pimlott.net>
Date
Jul 1, 2010, 19:40 UTC
Message-ID
<1278013199-sup-487@pimlott.net>
In-Reply-To
<1278012954-sup-3724@pimlott.net>

(forgot to mention I'm using git 1.7.1 from Debian package git-core 1:1.7.1-1)

Previous: Andrew PimlottNext: Björn Steinbrink
Message 2 of 13 in “git cherry not marking commits with equivalent upstream”
  1. Andrew PimlottJul 1, 2010
  2. Andrew PimlottJul 1, 2010
  3. Björn SteinbrinkJul 1, 2010
  4. Andrew PimlottJul 1, 2010
  5. Documentation: 'cherry' does not cope well with merges from upstreamJonathan Nieder, Jul 1, 2010
  6. Andrew PimlottJul 1, 2010
  7. Jonathan NiederJul 1, 2010
  8. Junio C HamanoJul 1, 2010
  9. Jonathan NiederJul 2, 2010
  10. Jonathan NiederJul 2, 2010
  11. Michael J GruberJul 2, 2010
  12. Jonathan NiederJul 2, 2010
  13. Michael J GruberJul 2, 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.