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

Re: Replacing a Remote Branch

From
BLbill lam <cbill.lam@gmail.com>
Date
Jul 24, 2010, 01:17 UTC
Message-ID
<20100724011752.GA3333@debian.b2j>
In-Reply-To
<201007232248.49520.trast@student.ethz.ch>
Птн, 23 Июл 2010, Thomas Rast писал(а):
> Since + overrides the non-ff check, this means that the remote side
> has receive.denyNonFastForwards (see man git-config) enabled (or a
> hook to the same effect).  Deleting and pushing the new branch merely

I also scratched my head why push --force failed to push an amend/rebase branch to assembla. IMO it would be nice to mention this receive.denyNonFastForwards inside man git-push.

-- 
regards,
====================================================
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
Previous: Eric James Michael RitzNext: Thomas Rast
Message 4 of 7 in “Replacing a Remote Branch”
  1. Eric James Michael RitzJul 23, 2010
  2. Thomas RastJul 23, 2010
  3. Eric James Michael RitzJul 23, 2010
  4. bill lamJul 24, 2010
  5. 1/2 Document receive.denyDeleteCurrentThomas Rast, Jul 24, 2010
  6. 2/2 Documentation/git-push: Explain status output in more detailThomas Rast, Jul 24, 2010
  7. 1/2 Document receive.denyDeleteCurrentThomas Rast, Jul 24, 2010

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.