On 2016-04-13, at 7:34 AM, Konstantin Khomoutov <flatw...@users.sourceforge.net> wrote: > > There's actually nothing to be surprised about: Git was explicitly > designed in a way to abstrain itself from managing authentication, > authorization and access controls. Hence, when a Git process is being > run to serve a push to a repository (or a fetch from it) it has no idea > about the identity -- whatever it could mean -- of the user who is > accesing that repository. That is, Git assumes some other software > handled the authentication+authorization+access controlling tasks.
There is nothing wrong with that design. However, if git is being given a --force option from the command line, and has standard input as a terminal, doesn't it make sense to put out a warning, "Force push can be destructive, and is not normal in most workflows. Do you really want to do this?", and read a Y/n response. --- Entertaining minecraft videos http://YouTube.com/keybounce -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
