James Henstridge wrote:So the "lightweight checkout" is equivalent of "lazy clone" we have much discussed on git mailing list about (without any resulting code, unfortunately). The point of problem was how to do this fast, without need for fast reliable connection to the repository it was cloned from. For example if to leave fetched objects in some kind of cache, or even in "lightweight checkout"/"lazy clone" repository database. If repository we do "lightweight checkout"/"lazy clone" from is on local file system (perhaps network file system), then we can use alternates mechanism (git clone -l -s). That's why "lazy clone" was sometimes named "remote alternates". We have terminology conflict here. Bazaar-NG "pull" and "merge" vs. GIT "fetch", "pull" and "merge"; Bazaar-NG "checkout" vs. GIT "clone" and "checkout". In GIT "clone" is what is used to copy whole repository, "checkout" is what is used to extract given/current branch to [given] working area. -- Jakub Narebski Poland - 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
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Andrew Morton | -mm merge plans for 2.6.23 |
| Greg Kroah-Hartman | [PATCH 025/196] paride: Convert from class_device to device for block/paride |
| Henrique de Moraes Holschuh | [RFC] rfkill class rework |
git: | |
| Gerrit Renker | [PATCH 05/37] dccp: Cleanup routines for feature negotiation |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Johann Baudy | Packet mmap: TX RING and zero copy |
| David Miller | [GIT]: Networking |
