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
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| Justin Piszcz | exception Emask 0x0 SAct 0x1 / SErr 0x0 action 0x2 frozen |
| Heiko Carstens | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
git: | |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Frans Pop | svc: failed to register lockdv1 RPC service (errno 97). |
| Radu Rendec | htb parallelism on multi-core platforms |
