AW: AW: git and concurrent access to local repository

From: Boettger, Heiko <heiko.boettger@karlstorz.com>
Date: Mar 23, 2016, 07:08 UTC
Message-ID: <8C0042D8869AEA4AA334B49AFBBCEF82B53CF604@TUT-EX02-PV.KSTG.corp>
In-Reply-To: <56F14E7F.3010801@web.de>

Hi Torsten,

yes, indeed I accidently pressed the wrong reply button.

The solution I'm using is the following:

pushd workingcopy > /dev/null
	(
		flock -x 200
		git reset --hard
		git clean -xfd
		git pull --rebase
	) 200>.git/gitrebase.lock
popd > /dev/null

Best Regards Heiko

-----Ursprüngliche Nachricht-----
Von: Torsten Bögershausen [mailto:tboegi@web.de] 
Gesendet: Dienstag, 22. März 2016 14:54
An: Boettger, Heiko
Betreff: Re: AW: git and concurrent access to local repository

Thanks for the reply, you may want to send it to all, including the git mailing list. These kindof problems arise from time to time, and it may be nice to share your knowledge as well, including work-arounds

On 2016-03-22 10.54, Boettger, Heiko wrote:

Show 6 quoted lines

> Thanks Torsten,
>
> for sharing your knowledge. That exactly what I thought. As a solution, I'm guarding the calls with "flock -x", which perfectly works since I know exactly where the repos are used. 
>
> Regards
> Heiko