On Wed, 10 Sep 2008, Paolo Bonzini wrote:Sure. I don't use them either. But because I don't use them, it doesn't affect me. It also doesn't change the core git data structures in any way to introduce any new problems. Also, if there isn't a required piece of history, things generally break very loudly. IOW, there are only certain things you can do with a shallow repo. In general it's absolutely _not_ a "no big deal" issue, quite the reverse - it's a deal-breaker. Linus -- 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
| Alan | Re: [RFC] Heads up on sys_fallocate() |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Paul Mundt | Re: 2.6.22-rc4-mm2 |
git: | |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | Re: [GIT]: Networking |
| Frans Pop | svc: failed to register lockdv1 RPC service (errno 97). |
