"KK" == Krzysztof Kosiński <tweenk.pl@...400...> writes:
KK> 1. No sequential revision numbers. Given commits 09fa34b3 and KK> 23e9f1a0 I can't tell which one is earlier. IIt appears the only KK> reason this was done is to be different from CVS, which Linus hates.
Sequential rev numbers are in generall not physically possible. But to the extent that they can ever work, git supports them via git describe and annotated tags. As an example. one of my kernel trees is now at version v2.6.38-rc4-177-g091994c, where v2.6.38-rc4 is the last annotated tag before that commit, 091994c is the hash of the commit, and 177 is the number of commits between them.
KK> 4. Several important manpages are nearly impossible to understand if KK> you don't already know what the command does.
All projects can benefit from better documentation. The git commiters have shown that they are amiable to patches which improve the quality of their documentation.
KK> 5. Poor support for checkout-update-commit workflow as seen in SVN. KK> Instead of checkout-update-commit, you have clone-pull-commit-push.
That is a non-distributed vs distribute issue. If other DVCSes try to hide that issue under the rug -- and I do not know that any do -- it will only jump out and bite their users in the end.
-JimC