Jeff King <peff <at> peff.net> writes: > > The short of it is that it's dangerous, we see people confused by it > (there was another one just yesterday), and it's a FAQ: > > http://git.or.cz/gitwiki/GitFaq#head-b96f48bc9c925074be9f95c0fce69bcece5f6e73 > > The FAQ even says "don't do this until you know what you are doing." So > the safety valve is configurable, so that those who know what they are > doing can switch it off. When I first tried to use git I was bitten by exactly this problem. I know, RTFM, but when everything is new, it's easy to undervalue the words of wisdom when you don't understand the bigger picture and the rational behind the advice. I now happily work with non-bare repositories on my main machine that I push to from my satellite development machines but, of course, I don't push to the head branches but, instead, to remote branches and then merge on the main machine. I wouldn't have wasted as much time getting my head around this if git had refused to accept the push to the current branch but, instead, issued a suitable message telling me I probably didn't want to be doing that. So, from my own experience, I would say this would be a good feature to add. Cheers, Mark -- 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
