git merge FETCH_HEAD produced bad commit message

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Michael S. Tsirkin
Date: Thursday, January 25, 2007 - 7:52 am

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
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
git merge FETCH_HEAD produced bad commit message, Michael S. Tsirkin, (Thu Jan 25, 7:52 am)
Re: git merge FETCH_HEAD produced bad commit message, Alex Riesen, (Fri Jan 26, 2:02 am)
Re: git merge FETCH_HEAD produced bad commit message, Michael S. Tsirkin, (Fri Jan 26, 7:24 am)
Re: git merge FETCH_HEAD produced bad commit message, Alex Riesen, (Fri Jan 26, 7:32 am)
Re: git merge FETCH_HEAD produced bad commit message, Michael S. Tsirkin, (Fri Jan 26, 7:42 am)