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

Re: [PATCH] Fix incorrect wording in git-merge.txt.

From
Matthieu Moy <matthieu.moy@imag.fr>
Date
Mar 3, 2008, 19:50 UTC
Message-ID
<vpqlk4zoacw.fsf@bauges.imag.fr>
In-Reply-To
<alpine.LFD.1.00.0803031320180.2899@xanadu.home>
Nicolas Pitre <nico@cam.org> writes:
> You don't really merge a commit _object_.
> You merge with one or more other commits, tipycally identified by a 
> branch name or a tag.

Strictly speaking, you can merge any commit, not necessarily a branch or a tag. That can be "git merge 66f0a4d" or whatever. Admitedly, the common case is to merge a tag or a branch (which is why I keep it in parentheses).

Now, I don't understand the distinction you seem to be making between "commit" and "commit object".

-- 
Matthieu
Previous: Nicolas PitreNext: Nicolas Pitre
Message 5 of 9 in “Fix incorrect wording in git-merge.txt.”
  1. Fix incorrect wording in git-merge.txt.Matthieu Moy, Mar 3, 2008
  2. Junio C HamanoMar 3, 2008
  3. Fix incorrect wording in git-merge.txt.Matthieu Moy, Mar 3, 2008
  4. Nicolas PitreMar 3, 2008
  5. Matthieu MoyMar 3, 2008
  6. Nicolas PitreMar 3, 2008
  7. Matthieu MoyMar 3, 2008
  8. Nicolas PitreMar 3, 2008
  9. Andreas EricssonMar 11, 2008

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.