On Tue, Mar 18 2008, Linus Torvalds wrote:Not to my knowledge, I haven't changed anything in my setup or behaviour in ages. The last few times it was: $ git checkout master $ git branch some-test-branch $ git checkout some-test-branch $ git pull . some-devel-branch and after that pull, I get to sit around waiting git gc. Well I don't since I ctrl-c it because it's inconvenient. But freshly pulled repo, git auto gc is enabled. And that is my main annoyance, I just don't think that type of policy should be in there. Print the warning, include info on how to run git gc or even how to turn it on automatically. But I'll bet you that most users will NOT want auto gc. Ever. -- Jens Axboe -- 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
| Amit K. Arora | [RFC] Heads up on sys_fallocate() |
| Rafael J. Wysocki | 2.6.27-rc4-git1: Reported regressions from 2.6.26 |
| Dave Hansen | Re: [RFC/PATCH] Documentation of kernel messages |
| Bart Van Assche | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Corey Minyard | [PATCH 3/3] Convert the UDP hash lock to RCU |
| Tomas Winkler | [PATCH] iwlwifi: RS small compile warnings without CONFIG_IWLWIFI_DEBUG |
