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

Re: [PATCH v2 0/7] clarify 'git merge' documentation

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 24, 2010, 19:29 UTC
Message-ID
<7v636r714n.fsf@alter.siamese.dyndns.org>
In-Reply-To
<201001241425.07027.trast@student.ethz.ch>
Thanks, pulled.
Previous: Thomas Rast
Message 11 of 11 in “clarify 'git merge' documentation”
  1. 0/7 clarify 'git merge' documentationJonathan Nieder, Jan 23, 2010
  2. 1/7 Documentation: merge: move configuration section to endJonathan Nieder, Jan 23, 2010
  3. 2/7 Documentation: suggest `reset --merge` in How Merge Works sectionJonathan Nieder, Jan 23, 2010
  4. 3/7 Documentation: merge: move merge strategy list to endJonathan Nieder, Jan 23, 2010
  5. 4/7 Documentation: merge: add an overviewJonathan Nieder, Jan 23, 2010
  6. Raja R HarinathFeb 12, 2010
  7. 5/7 Documentation: emphasize when git merge terminates earlyJonathan Nieder, Jan 23, 2010
  8. 6/7 Documentation: merge: add a section about fast-forwardJonathan Nieder, Jan 23, 2010
  9. 7/7 Documentation: simplify How Merge WorksJonathan Nieder, Jan 23, 2010
  10. Thomas RastJan 24, 2010
  11. Junio C HamanoJan 24, 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.