Steffen Prohaska <prohaska@xxxxxx> writes: > Users typically want to set the default for their account. Thus, > start the hint with how to achieve that; and only later explain > how to restrict identity to a single repository. If this were about the introductory part of the user manual, I would definitely vote for suggesting the --global one first as the baby steps will be done with one practice/sandbox repository and then when the user graduates to work on other projects and possibly under a different identity, it would make sense to introduce the non global one as an advanced option. > I watched someone setting up git, who never used it before. > The hint was leading him into the wrong direction. Real-life new user experience is a very valuable one. Can you elaborate how the hint led in a _wrong_ direction? What is the definition of "wrong" here? It may be that not using --global is perfectly the correct thing to do. It really depends on the project and the situation. The condition to cause this error message to be shown is probably a borderline, compared to the earlier "introductory part of the manual" case. You may have set an identity in one repository without global, and then switched to another repository and saw this message. In which case you may want to use a different identity or the same one and I would not say which one is more common in the case for such a "second repository". When you work on two projects, managed by two different organizations, it often is that you would want per-repository identity. Was this the first repository for this person to set up? - 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
