Hi, Dear diary, on Fri, Aug 18, 2006 at 12:21:11PM CEST, I got a letter where Johannes Schindelin <Johannes.Schindelin@xxxxxx> said that... > However, you should know that there is _no way_ to use both hashes on the > same project. Yes, you could rewrite the history, trying to convert also > the hashes in the commit objects, but people actually started relying on > naming commits with the short-SHA1. I don't really like having IDs ambiguous in this sense - having the same type of IDs in all git-tracked projects has some cute benefits which are of the kind that you don't know ahead that you will need them: joining history of two distinct projects in a merge and theoretical possibility of having subprojects where the main project references an exact tree/commit of the sub project. If we are ever going to implement support for multiple hashes, the hash type should at least be part of the object id, in textual representation as e.g. the first letter. This can still lead to convergence issues and duplicate objects, but it enables smooth transition without rewriting the history and it is much less confusing than just switching to a different function. -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ Snow falling on Perl. White noise covering line noise. Hides all the bugs too. -- J. Putnam - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html