I also like the feature of being able to fetch commits by SHA-1. My problem is that it is not clear to end users whether they can fetch SHA-1 from a specific server or not. For exactly the same server a "git fetch origin <id-of-commit-x>" first doesn't work and all of the sudden that command works and updates e.g. FETCH_HEAD. That's because between the first and the second fetch you fetched that commit already by fetching a branch.
And even if the commit is known only to the local repo then the fetch works. I tried to fetch a commit which I just created locally. And the output is: > git fetch eclipse 382dfeab0e11bd88388d7195114c046c3ec27d8f >From https://git.eclipse.org/r/jgit/jgit * branch 382dfeab0e11bd88388d7195114c046c3ec27d8f -> FETCH_HEAD This gives me the impression that that update was triggered by data coming from the server https://git.eclipse.org/r/jgit/jgit. But the server doesn't know the commit. In my eyes the fetch should fail if the server doesn't know the commit. Ciao Chris -- 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
