From: Matthias Urlichs Date: Tue, 29 Nov 2005 12:14:07 GMT Subject: Re: [PATCH] Re: keeping remote repo checked out? Message-ID: In-Reply-To: Hi, Daniel Barkalow wrote: > That's what I'm doing currently, actually (with work pushing to > "production", but server having checked out "deploy"), and I find it > annoying to have to do the pull each time and have a separate head. Why? I think "what's currently deployed" and "the latest commit on the production branch" are two distinct concepts, and should be treated as such. That way, a clean push (update of PRODUCTION, controlled by the update hook) and an update of DEPLOY (the fast-forward merge (unless you need to roll back something) from your production branch, controlled by the post-update hook) are also distinct, can be handled individually. Personally I just use "git-read-tree -m -u deploy master && \ cat refs/heads/master > refs/heads/deploy" in the post-update trigger. I don't care about HEAD at all; nobody is supposed to change that directory manually anyway. -- Matthias Urlichs | {M:U} IT Design @ m-u-it.de | smurf@smurf.noris.de Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de - - Bringing computers into the home won't change either one, but may revitalize the corner saloon.