Re: No fchmd. was: Re: [PATCH 00/14] Add submodule test harness

2014-07-10 Thread Junio C Hamano
Torsten Bögershausen writes: > On 2014-07-10 21.49, Junio C Hamano wrote: > [] >> If we limit the case to "Inherit permissions from the file we are >> replacing by taking a lock on it", which is the topic of discussion >> in this thread, we do not have to worry about how to configure the >> value

Re: No fchmd. was: Re: [PATCH 00/14] Add submodule test harness

2014-07-10 Thread Torsten Bögershausen
On 2014-07-10 21.49, Junio C Hamano wrote: [] > If we limit the case to "Inherit permissions from the file we are > replacing by taking a lock on it", which is the topic of discussion > in this thread, we do not have to worry about how to configure the > value (we do not have to) and adding a new p

Re: No fchmd. was: Re: [PATCH 00/14] Add submodule test harness

2014-07-10 Thread Junio C Hamano
Torsten Bögershausen writes: > Isn't the whole problem starting here: > in config.c: > > fd = hold_lock_file_for_update(lock, config_filename, 0); > In lockfile.c: > /* This should return a meaningful errno on failure */ > int hold_lock_file_for_update(struct lock_file *lk, const char > *

No fchmd. was: Re: [PATCH 00/14] Add submodule test harness

2014-07-09 Thread Torsten Bögershausen
On 07/09/2014 11:57 PM, Junio C Hamano wrote: Eric Wong writes: Junio C Hamano wrote: Johannes Sixt writes: Am 08.07.2014 21:34, schrieb Jens Lehmann: And Msysgit complains error: fchmod on c:/xxxt/trash directory.t7613-merge-submodule/submodule_update_repo/.git/modules/sub1/config.lock