Hi, On Fri, 21 Jul 2006, Petr Baudis wrote: > Yes, there is some blury stuff, but I think it's rather a sign that > something is missing in the core Git porcelain. git-init-db is lowlevel > and I think in 99% of the cases you are going to do an initial commit > right after anyway, so you might as well just get git-init which does it > for you (something akin cg-init ;). Think "changed templates". And also think "setup a remote repository", especially "setup a remote HTTP repository". No, clone will not work if you are sitting behind a firewall and/or DSL router (and who does not?). And also think "start a new repository with only a _part_ of the current files". There are plenty reasons -- in addition to separation of concepts -- not to commit straight after initializing a repository. > I think we still tell users to use git-update-index to mark resolved > conflicts, [...] I don't know, but I had the impression we'd tell them "resolve your conflicts, and then do git-commit -a". Which is good enough. Ciao, Dscho - : 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