On 1/26/07, Michael S. Tsirkin <mst@mellanox.co.il> wrote: > > Does it need to? > > FETCH_HEAD is not a real head name, so I think the message above is a bug. > For whatever Git cares - it is a real reference. > > Is the below enough (could be line-wrapped): > > > > git merge --no-commit FETCH_HEAD && \ > > git commit -M "Merge $(cut -d ' ' -f 2- < $(git rev-parse > > --git-dir)/FETCH_HEAD) \ > > into $(git name-rev HEAD | cut -d ' ' -f 2-)" > > Or I can just commit --amend and edit it manually. > But that's not the point. What is the point then? It looked like you were complaining it were not done automatically. I showed you how to script it. The message can be made to look exactly as it is for git-pull. So what's wrong? > > In the long run you'll almost certainly find this commit message > > useless, though. > > Isn't 'Merge ssh://<hidden>/usr/src/ofed_1_2 info ofed_1_2' much more > useful than Merge commit 'FETCH_HEAD'? What for? Isn't "Merge origin/ofed_1_2 into ofed_1_2" much more useful than "Merge FETCH_HEAD"? (IOW: Why don't you just save the fetch result somewhere and have a "source description" from that?) - 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.htmlReceived on Sat Jan 27 01:34:03 2007
This archive was generated by hypermail 2.1.8 : 2007-01-27 01:37:47 EST