From: Marc Branchaud <marcnarc@xiplink.com>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: git@vger.kernel.org, gitster@pobox.com, philipoakley@iee.org,
artagnon@gmail.com, marcnarc@xiplink.com
Subject: Re: [PATCH] Documentation/git-push.txt: explain better cases where --force is dangerous
Date: Mon, 17 Jun 2013 17:09:48 -0400 [thread overview]
Message-ID: <51BF7B1C.2040703@xiplink.com> (raw)
In-Reply-To: <1371491561-19117-1-git-send-email-Matthieu.Moy@imag.fr>
On 13-06-17 01:52 PM, Matthieu Moy wrote:
> The behavior of "git push --force" is rather clear when it updates only
> one remote ref, but running it when pushing several branches can really
> be dangerous. Warn the users a bit more and give them the alternative to
> push only one branch.
>
> Signed-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>
> ---
> Documentation/git-push.txt | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
> index 938d1ee..9b9e7d1 100644
> --- a/Documentation/git-push.txt
> +++ b/Documentation/git-push.txt
> @@ -136,6 +136,14 @@ already exists on the remote side.
> not an ancestor of the local ref used to overwrite it.
> This flag disables the check. This can cause the
> remote repository to lose commits; use it with care.
> + Note that `--force` applies to all the refs that are pushed,
> + hence using it with `push.default` set to `matching` or with
> + multiple push destination configured may override refs other
s/destination/destinations/
M.
next prev parent reply other threads:[~2013-06-17 21:16 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 [this message]
2013-06-17 21:38 ` Junio C Hamano
2013-06-18 7:42 ` Matthieu Moy
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51BF7B1C.2040703@xiplink.com \
--to=marcnarc@xiplink.com \
--cc=Matthieu.Moy@imag.fr \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).