Am 17.03.2015 um 08:28 schrieb Jeff King:
+test_expect_success 'create history reachable only from a bogus-named ref' '
+       test_tick && git commit --allow-empty -m master &&
+       base=$(git rev-parse HEAD) &&
+       test_tick && git commit --allow-empty -m bogus &&
+       bogus=$(git rev-parse HEAD) &&
+       git cat-file commit $bogus >saved &&
+       echo $bogus >.git/refs/heads/bogus:name &&

This causes headaches on Windows: It creates an empty file, named "bogus", with all the data diverted to the alternate data stream named "name". Needless to say that this...

+test_expect_success 'clean up bogus ref' '
+       rm .git/refs/heads/bogus:name
+'

does not remove the file "bogus", but only the alternate data stream (if at all---I forgot to check). How about .git/refs/heads/bogus..nam.e?

-- Hannes

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to