Revision ad65f7e3b71aac841d771cd75392747d6945cc3c authored by Ben Wijen on 18 August 2016, 14:51:12 UTC, committed by Junio C Hamano on 18 August 2016, 20:56:45 UTC
On Windows, a file cannot be removed unless all file handles to it have been released. Hence it is particularly important to close handles when spawning children (which would probably not even know that they hold on to those handles). The example chosen for this test is a custom merge driver that indeed has no idea that it blocks the deletion of index.lock. The full use case is a daemon that lives on after the merge, with subsequent invocations handing off to the daemon, thereby avoiding hefty start-up costs. We simulate this behavior by simply sleeping one second. Note that the test only fails on Windows, due to the file locking issue. Since we have no way to say "expect failure with MINGW, success otherwise", we simply skip this test on Windows for now. Signed-off-by: Ben Wijen <ben@wijen.net> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
1 parent e0c1cea
mailmap.h
#ifndef MAILMAP_H
#define MAILMAP_H
int read_mailmap(struct string_list *map, char **repo_abbrev);
void clear_mailmap(struct string_list *map);
int map_user(struct string_list *map,
const char **email, size_t *emaillen, const char **name, size_t *namelen);
#endif
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...