On Tue, Jul 15, 2008 at 04:27:02PM +0100, Johannes Schindelin wrote:If you just grab sources and never read release notes, there is nothing that can help you. If Git 1.6.0 is not the right moment to do these changes then Git 1.6.1 is neither, regardless whether Debian will release Lenny by that time or not. People do not upgrade their distro in the day of release. Some upgraded to Etch not so long ago. So, should we wait for another year till 1.7.0? I don't think Git 1.4 is easy to use. If you want Git that is easy to use install Git 1.5.x. And, it is *much* easier to install Git from backports then to deal with usability issues of Git 1.4 and the lack of community support. So, I don't see how this change may hurt. It has *nothing* to do with making easy on ourselves and hard on others. The question here is what is the appropriate time to change these default settings, and I believe that *major* releases are the appropriate time while minor ones are not. Dmitry -- 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
| Thomas Gleixner | Re: Linux 2.6.21-rc1 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| James Bottomley | [Ksummit-2008-discuss] Fixing the Kernel Janitors project |
| James Morris | Re: LSM conversion to static interface |
git: | |
| Natalie Protasevich | [BUG] New Kernel Bugs |
| Christoph Hellwig | Re: [PATCH 06/32] IGET: Mark iget() and read_inode() as being obsolete [try #2] |
| Linus Torvalds | Re: [GIT]: Networking |
| Jarek Poplawski | [PATCH take 2] pkt_sched: Protect gen estimators under est_lock. |
