Re: Minor annoyance with git push

From: Jay Soffian <jaysoffian@gmail.com>
Date: Feb 20, 2008, 15:20 UTC
Message-ID: <76718490802200720w4dd89dc1lf7b19d546d3bfd00@mail.gmail.com>
In-Reply-To: <alpine.LSU.1.00.0802201305350.17164@racer.site>

On Feb 20, 2008 8:06 AM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

Show 13 quoted lines

> Hi,
>
> On Wed, 20 Feb 2008, Junio C Hamano wrote:
>
> > Putting this "push = HEAD" by default when "git clone" and "git remote
> > add" creates the [remote "$remote"] section is probably possible, and at
> > that stage we may even be able to do the "if the other end is shared,
> > then set this up automagically", as the result of the magic can be
> > inspected in the resulting config file.
>
> I think this is too magic, both of it.  Once people get used to "git push"
> being implicitly "git push origin HEAD", why should they not expect "git
> push <somewhere-else>" to push "HEAD" implicitly, too?

Well then, how about (don't cringe too much now...)

  push.conservative = true

If enabled and "git push" is run w/o arguments, it will first emit what it plans to push and then prompt with "yes/no." I'm kinda opposed to silly prompts -- folks just always go right past them -- so I dunno.

But it does make the operation a bit more safe I guess.

j.