git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Documentation/git-push.txt: explain better cases where --force is dangerous

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Jun 18, 2013, 07:42 UTC
Message-ID
<vpq38sfx3ty.fsf@anie.imag.fr>
In-Reply-To
<7v7ghsbeoo.fsf@alter.siamese.dyndns.org>
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/
Previous: Junio C HamanoNext: Junio C Hamano
Message 5 of 6 in “Documentation/git-push.txt: explain better cases where --force is dangerous”
  1. Documentation/git-push.txt: explain better cases where --force is dangerousMatthieu Moy, Jun 17, 2013
  2. Junio C HamanoJun 17, 2013
  3. Marc BranchaudJun 17, 2013
  4. Junio C HamanoJun 17, 2013
  5. Matthieu MoyJun 18, 2013
  6. Junio C HamanoJun 18, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.