{"push_id":937404816,"size":1,"distinct_size":0,"ref":"refs/heads/js/dirname-basename","head":"371471cea38cb4b5834c9e5715e1fe633829004f","before":"8753c96da4abc0e53bc320772b08161a16a8c7c1","commits":[{"sha":"371471cea38cb4b5834c9e5715e1fe633829004f","author":{"email":"53fb8db7833fca1e1746dd8592f61048d350f64c@gmx.de","name":"Johannes Schindelin"},"message":"t0060: loosen overly strict expectations\n\nThe dirname() tests file were developed and tested on only the five\nplatforms available to the developer at the time, namely: Linux (both 32\nand 64bit), Windows XP 32-bit (MSVC), MinGW 32-bit and Cygwin 32-bit.\n\nhttp://pubs.opengroup.org/onlinepubs/9699919799/functions/basename.html\n(i.e. the POSIX spec) says, in part:\n\n\tIf the string pointed to by path consists entirely of the '/'\n\tcharacter, basename() shall return a pointer to the string \"/\".\n\tIf the string pointed to by path is exactly \"//\", it is\n\timplementation-defined whether \"/\" or \"//\" is returned.\n\nThe thinking behind testing precise, OS-dependent output values was to\ndocument that different setups produce different values. However, as the\ntest failures on MacOSX illustrated eloquently: hardcoding pretty much each\nand every setup's expectations is pretty fragile.\n\nThis is not limited to the \"//\" vs \"/\" case, of course, other inputs are\nalso allowed to produce multiple outputs by the POSIX specs.\n\nSo let's just test for all allowed values and be done with it. This still\ndocuments that Git cannot rely on one particular output value in those\ncases, so the intention of the original tests is still met.\n\nSigned-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/gitster/git/commits/371471cea38cb4b5834c9e5715e1fe633829004f"}]}