On Wed, Oct 24, 2007 at 11:06:24PM +0200, Andreas Ericsson wrote:You can't check what got added in your pull, e.g you can't review the new code with something like gitk next..origin/next I often do something like this, just to see what got changed. So at least in my opinion you have to add a third point: * the branch has no modifications what so ever * the branch is set up to auto-merge with the particular branch fetched from the particular remote AND * the user set a config option to always autofastfoward if the above conditions are true! This could be implemented as a global option with a per branch overwrite. Only if this option is added so a user can mark a branch to never autofastforward (but it is still possible to have an auto-merge config) you won't loose valuable information. -Peter - 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
| Avi Kivity | [PATCH 09/58] KVM: MMU: Respect nonpae pagetable quadrant when zapping ptes |
| Andrew Morton | 2.6.25-rc2-mm1 |
| James Morris | Re: LSM conversion to static interface |
| Eric W. Biederman | Re: [PATCH] kexec: force x86_64 arches to boot kdump kernels on boot cpu |
git: | |
| David Miller | Re: 2.6.25-rc8: FTP transfer errors |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [GIT *] Solos PCI ADSL card update |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
