Am Tue, 16 Oct 2012 13:36:04 +0200 schrieb Angelo Borsotti <angelo.borsotti@xxxxxxxxx>: > Hello, > > some VCS, e.g. ClearCase, allow to control the fetching of files so as > to warn, or > disallow parallel changes to the same files. > As of today, there is no way to implement the same kind of workflow > with git because there are no fetch hooks. > Would it be a good idea to provide them? I've actually implemented a 'git lock' command to lock pathnames from concurrent editing for a customer. Normally one would say this is a rather ill and ugly feature for git but there where some reasons to do it anyways (imagine robots crashing into each other on a production line because of bad (developer-)communication). The code is GPL and I can distribute it, but I didn't consider it ready for an open announcement yet. Noteworthy some problems with msys led to some ugly solution (the uniq command doesn't know the -z option there). I hope this might be useful to you. I'd also like to get contributions and fixes if there are any problems I am not aware of. Short into; the doc: http://git.pipapo.org/?p=git;a=blob_plain;f=Documentation/git-lock.txt;h=dcc7a5c34dea657ab5819e8def54e154d5d97219;hb=25ee09cf35daa03a7c2ef10537561a50db2d17b2 the code is available at git://git.pipapo.org/git in the 'ct/git-lock' branch. It is a bit fallen behind the current git version, I will update/merge it sometime next (to keep in par with msysgit, thats what is required here) Christian > > -Angelo Borsotti > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html