Re: pull/merge --no-commit

From: Keith Duthie <keith@no.net.nz>
Date: Jun 7, 2007, 20:51 UTC
Message-ID: <alpine.DEB.0.99.0706080841030.6319@sleipnir.no.net.nz>
In-Reply-To: <46686B63.6080808@alcatel-lucent.com>

On Thu, 7 Jun 2007, kurt_p_lloyd wrote:

> Just an idea.  Of course, if something like this already exists ....
> (I'd rather not shut down sshd, nor have to create a separate "public"
>  repository (for certain types of "projects" anyway).)

Actually, a separate public repository is probably exactly what you want here. If you clone the repository with the local and shared flags you'll only need to have one copy of the objects on disk (if I understand things correctly), and you can just push your development branch to the public repository whenever you're happy with the state of your code.

And if you're going to give other people access to your development repository then you're probably best off having a branch (or branches) that are there specifically for other people to pull from, and make sure you don't merge anything into those branches without it being ready for release. And then tell people it's their own fault if they grab one of your work-in-progress branches instead ;-)

-- 
The universe hates you, but don't worry - it's nothing personal.