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

Re: push to backup repo periodically fails with "not fast forward"

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Dec 22, 2008, 17:19 UTC
Message-ID
<94a0d4530812220919t25233fa9ub461c86f10ec366d@mail.gmail.com>
In-Reply-To
<f95d47890812220915h5286d2bdv7c8412ecf77be999@mail.gmail.com>
On Mon, Dec 22, 2008 at 7:15 PM, David Copeland <davetron5000@gmail.com> wrote:
Show 6 quoted lines
> the original gets rebased from a git svn rebase on occasion; so I
> guess that is causing things to not be fast-forward.
>
> I guess all I really want to do is keep a duplicate copy of my repo
> somewhere else.  Should I just use --force in my hook, or abandon git
> as the mechanism and use rsync?

I would manually do 'git push backup' at certain points since not all my commits are meant to be backed up, specially on temporal feature branches.

But --force should do the trick.
-- 
Felipe Contreras
Previous: David CopelandNext: Nicolas Pitre
Message 4 of 5 in “push to backup repo periodically fails with "not fast forward"”
  1. davetron5000Dec 22, 2008
  2. Felipe ContrerasDec 22, 2008
  3. David CopelandDec 22, 2008
  4. Felipe ContrerasDec 22, 2008
  5. Nicolas PitreDec 22, 2008

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.