All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Scott Chacon <schacon@gmail.com>
Cc: sylvain@abstraction.fr, git@vger.kernel.org, howard@e-learndesign.co.uk
Subject: Re: How to ignore changes on remote
Date: Tue, 23 Mar 2010 09:44:43 -0700	[thread overview]
Message-ID: <7vtys72dj8.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <d411cc4a1003230905y12839743x400333a0aa2e7018@mail.gmail.com> (Scott Chacon's message of "Tue\, 23 Mar 2010 09\:05\:41 -0700")

Scott Chacon <schacon@gmail.com> writes:

> Why would we teach someone to do that instead of just recommending the
> far less obscure 'git push -f'?  A leading '+' on the refspec is
> ridiculously confusing compared to "just tell it to force the push
> with -f".  Am I forgetting something?

I think "-f" would be simpler and easier for people who use only one
branch, as there is no "I want to disable only for this branch but still
want other branches checked" problem in such a case.

Once they graduate from that and start using more than one branches, "-f"
is too broad a brush that disables the check for everything you push out,
and you would want to teach "+" as a way to narrow the possible damage.

"git push -f origin this_branch_only" can be used to limit the risk, but
if they start from a short-and-lazy "git push -f" without arguments, their
finger would have harder time to learn it.  There is no such learning
curve issue for "+", as you cannot use it without saying for which branch
to disable the check.

      parent reply	other threads:[~2010-03-23 16:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-23 13:54 How to ignore changes on remote Howard Miller
2010-03-23 14:07 ` Sylvain Rabot
2010-03-23 14:13   ` Howard Miller
2010-03-23 14:21     ` Alexander Iljin
2010-03-23 14:22     ` Santi Béjar
2010-03-23 14:24       ` Howard Miller
2010-03-23 14:25     ` Sylvain Rabot
2010-03-23 16:05       ` Scott Chacon
2010-03-23 16:13         ` Howard Miller
2010-03-23 16:20         ` Johannes Sixt
2010-03-23 17:20           ` Johan Herland
2010-03-23 17:47             ` Jakub Narebski
2010-03-23 18:02               ` Johan Herland
2010-03-23 16:44         ` Junio C Hamano [this message]

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=7vtys72dj8.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=howard@e-learndesign.co.uk \
    --cc=schacon@gmail.com \
    --cc=sylvain@abstraction.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.