"Tom Clarke" <tom@u2i.com> writes:Very well put; I like concise summary of the point in a discussion thread like this. And the question in your last sentence is not merely incidental, but I think is the most crucial one to decide which way we should proceed. I do not offhand think of a place other than "git pull" that would make sense to sometimes be able to rebase when you normally use merge, so I am inclined to say it would be easier to teach that "'git pull' is usually a 'git fetch' followed by 'git merge', but in certain workflow it is handier to 'git fetch' and then 'git rebase', and here are the ways to get the rebasing behaviour...". - 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
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Vladislav Bolkhovitin | Re: Integration of SCST in the mainstream Linux kernel |
| Andrew Morton | -mm merge plans for 2.6.23 |
| Can E. Acar | Re: Wasting our Freedom |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| PJ Waskiewicz | [ANNOUNCE] ixgbe: Data Center Bridging (DCB) support for ixgbe |
