Re: keeping remote repo checked out?

From: Petr Baudis <pasky@suse.cz>
Date: Nov 28, 2005, 10:57 UTC
Message-ID: <20051128105736.GO22159@pasky.or.cz>
In-Reply-To: <7vbr051ad1.fsf@assigned-by-dhcp.cox.net>

Dear diary, on Mon, Nov 28, 2005 at 08:48:26AM CET, I got a letter where Junio C Hamano <junkio@cox.net> said that...

Show 10 quoted lines

> James Cloos <cloos@jhcloos.com> writes:
> 
> > Is it possible to arrange that a push does a checkout on the remote
> > the same way a pull does on the local?
> 
> Creative use of hooks/post-update would solve that.
> 
> However, you should be very careful if you sometimes edit on
> server and sometimes push from other machine to the server on
> the same branch on the server.

Why? At worst you will get files with conflict markers on the server, which isn't that huge problem and just what you have to expect when you do this kind of thing. I could imagine having an option in the config file describing whether the repository is "raw" or has the working copy associated, and in the later case have the updating code in the default post-update hook.

PS: If someone is bored, it would be very useful to have a manual page
for the git configuration file, containing the list of all options.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.