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

git merge FETCH_HEAD produced bad commit message

From
MTMichael S. Tsirkin <mst@mellanox.co.il>
Date
Jan 25, 2007, 14:52 UTC
Message-ID
<20070125145229.GE25265@mellanox.co.il>
Hi!
I like to do
	$git fetch <URL>
	$git log FETCH_HEAD
	
	$git merge FETCH_HEAD
I would expect this to be equivalent to
	git pull <URL>
	
However, the message that git merge produces in this case
is less than informative:
commit 3c11f564846227d80aa76b579c974913c3602862
Merge: 9871244... f5e6d63...
Author: Michael S. Tsirkin <mst@mellanox.co.il>
Date:   Thu Jan 25 16:46:51 2007 +0200
    Merge commit 'FETCH_HEAD' into ofed_1_2

I note that FETCH_HEAD actually has the information on where the commit came from: $cat .git/FETCH_HEAD f5e6d63839970f4785c36b6be3835f037e74195c ssh://<hidden>/usr/src/ofed_1_2

So can not git merge be enhanced to put this data in commit log?
-- 
MST
Next: Alex Riesen
Message 1 of 5 in “git merge FETCH_HEAD produced bad commit message”
  1. Michael S. TsirkinJan 25, 2007
  2. Alex RiesenJan 26, 2007
  3. Michael S. TsirkinJan 26, 2007
  4. Alex RiesenJan 26, 2007
  5. Michael S. TsirkinJan 26, 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.