Hello everyone, I am trying to fetch a commit using a commit ID instead of a reference. According to the documentation of git-fetch, this is not supported, but I found out that this is not entirely true.
If the commit is already available in the repository, I get: $ git fetch origin 7365b1a9bd45fbf12b09381d5779b607e232a8cd >From repo1 * branch 7365b1a9bd45fbf12b09381d5779b607e232a8cd -> FETCH_HEAD $ echo $? 0 If the commit is not in the repository (but it is present in the remote of course), I get: $ git fetch origin fc907b94f69b9bd710ba55b5522258b722fefb3b $ echo $? 1 That brings up following questions/remarks: - the documentation of git-fetch is not entirely correct, commit ids are partially supported, not only refs - “git fetch origin fc907” should print an error message on STDERR specifying what the problem is - more interestingly: is there any reason why git fetch should not support fetching by commit id? There are real world use cases where this can be very useful, for instance when references on the remote have been overwritten or deleted. Olivier -- 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
