On Wed, 13 Apr 2016 08:37:35 -0700
Michael <keybou...@gmail.com> 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.
My opinion is that this is counter-productive as the users will very
quickly learn to hit Y. I've seen that more than once. Off the top of
my memory, I recall 'rm' being aliases to 'rm -i' for root shells on
older released of Red Hat operating systems. That option asks the user
if they really want to delete the file. Guess what -- the user learns
to just hit y+Return each time or pass '-f' to override '-i'.
I mean, you either think before you do, or you don't.
(On a side note, I'd recommend reading the book "Turn the ship around!"
-- its part which deals with the so-called "deliberate action".)
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
For more options, visit https://groups.google.com/d/optout.