On 17/10/06, Sean <seanlkml@sympatico.ca> wrote:There are two forms of checkout: a normal checkout which contains the complete history of the branch, and a lightweight checkout, which just has a pointer back to the original location of the history. In both cases, a "bzr commit" invocation will commit changes to the remote location. In general, you only want to use a lightweight checkout when there is a fast reliably connection to the branch (e.g. if it is on the local file system, or local network). Aaron would be talking about a normal (heavyweight) checkout here. With a heavyweight checkout, you can do pretty much anything without access to the branch. In contrast, almost all operations on a lightweight checkout need access to the branch. James. - 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
| Bart Van Assche | Re: Integration of SCST in the mainstream Linux kernel |
| Greg KH | 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 |
| Andrew Morton | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| David Miller | [GIT]: Networking |
| Radu Rendec | htb parallelism on multi-core platforms |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
