From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: Marc Branchaud <marcnarc@xiplink.com>,
git@vger.kernel.org, philipoakley@iee.org, artagnon@gmail.com
Subject: Re: [PATCH] Documentation/git-push.txt: explain better cases where --force is dangerous
Date: Tue, 18 Jun 2013 09:42:17 +0200 [thread overview]
Message-ID: <vpq38sfx3ty.fsf@anie.imag.fr> (raw)
In-Reply-To: <7v7ghsbeoo.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Mon, 17 Jun 2013 14:38:47 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> After I re-read the one, I found that "override" somewhat a strange
> expression. There is nothing that overrides or to be overriden.
Right, I actually meant "overwrite".
> How about putting it like this?
I'm not sure "push out refs other than the current branch" is strong
enough. Once you are used to "push = fast-forward = can't loose data",
"push out a ref" is not very scary.
I'd do s/push out/overwrite/, but I'm fine with your version too.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2013-06-18 7:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 17:52 [PATCH] Documentation/git-push.txt: explain better cases where --force is dangerous Matthieu Moy
2013-06-17 19:36 ` Junio C Hamano
2013-06-17 21:09 ` Marc Branchaud
2013-06-17 21:38 ` Junio C Hamano
2013-06-18 7:42 ` Matthieu Moy [this message]
2013-06-18 14:35 ` Junio C Hamano
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=vpq38sfx3ty.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=marcnarc@xiplink.com \
--cc=philipoakley@iee.org \
/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).