git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: John Tapsell <johnflux@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git push
Date: Tue, 24 Feb 2009 23:01:38 -0800	[thread overview]
Message-ID: <7vskm3c84t.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <43d8ce650902242238s7ab4c851p9c820c96b67aa62b@mail.gmail.com> (John Tapsell's message of "Wed, 25 Feb 2009 06:38:41 +0000")

John Tapsell <johnflux@gmail.com> writes:

>   Following the idea of 'least damage', what do people think of making
> "git push" only push the branch you are currently on?

Having an easy way to ask to push only one branch (typically the currently
checked-out one) is a good thing.  You can obviously say "git push origin
master" (or whatever branch you are on).  We also added "git push origin
HEAD".  I thought we even added "git push HEAD" or "git push --current",
but I may be mistaken.

But if you are talking about changing the default when "git push" is run
without any parameter, I have to say it is a terrible idea, for two
reasons, and one is too obvious to state so I wouldn't repeat it and talk
only about the other one.

I've noticed that people who ask for such a default tend to push too often
and worse they tend to push before they have their act together.  Surely
their other branches may not be ready, but it is likely their current
branch isn't either ;-)

If you shoot for the least damage for such people, the sanest default for
"git push" would be to do nothing.  You *always* say what to push where,
then there is no risk of pushing something you did not intend to.  Perhaps
"push.default = never" configuration may not be such a bad idea?

  parent reply	other threads:[~2009-02-25  7:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25  6:38 git push John Tapsell
2009-02-25  6:46 ` Jeff King
2009-02-25  7:01 ` Junio C Hamano [this message]
2009-02-25  7:09   ` John Tapsell
2009-02-25  7:44     ` Junio C Hamano
2009-02-25  9:02       ` Jeff King
2009-02-25  9:26         ` Junio C Hamano
2009-02-25  9:51           ` Jeff King
2009-02-25  9:08       ` John Tapsell
2009-02-25  9:49         ` Junio C Hamano
2009-02-25 10:06           ` John Tapsell
2009-02-25  9:34       ` Jay Soffian
2009-02-25  9:51         ` Junio C Hamano
2009-02-25 22:58   ` Finn Arne Gangstad
2009-03-05  8:45     ` Andreas Ericsson
2009-03-05  8:56       ` John Tapsell
2009-03-05  9:44       ` Finn Arne Gangstad
     [not found] <CAJmx4Nxh_WzkO-S=SN9E=aODCrfs+QCig4sT+Q8eQ+Pv1hB2+w@mail.gmail.com>
2012-03-19 16:24 ` Kevin O'Brien

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vskm3c84t.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=johnflux@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).