Hi, git merge --no-commit <branch> does "create" a commit. At lesat the head and index are moved to the new commit fetched from <branch>. Maybe that is because git was able to do a fast forward? Cheers, Michael - 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
| Ryan Hope | reiser4 for 2.6.27-rc1 |
| Paul Menage | Re: [RFC][PATCH 6/7] Account for the number of tasks within container |
| Glauber de Oliveira Costa | [PATCH 1/19] unify desc_struct |
| David Woodhouse | Re: OT: character encodings (was: Linux 2.6.20-rc4) |
git: | |
| Eric Wong | Re: [RFC] Git config file reader in Perl (WIP) |
| Junio C Hamano | [PATCH/POLL] git-format-patch: the default suffix is now .patch, not .txt |
| Martin Langhoff | Re: pack operation is thrashing my server |
| Franck Bui-Huu | Re: [PATCH 1/2] Add git-archive |
| Chris Bullock | OpenBSD isakmpd and pf vs Cisco PIX or ASA |
| Richard Stallman | Real men don't attack straw men |
| Axton | Re: rouge IPs / user |
| Hannah Schroeter | Re: Improving disk reliability |
| Andi Kleen | [PATCH RFC] [4/9] modpost: Fix format string warnings |
| Jeff Garzik | Re: [regression] e1000e broke e1000 |
| Linus Torvalds | Re: [GIT]: Networking |
| Pekka Enberg | Re: [rfc][patch 1/3] slub: fix small HWCACHE_ALIGN alignment |
