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:11 UTC
Message-ID
<94a0d4530812220911l37b825edj55178658f24755c1@mail.gmail.com>
In-Reply-To
<19016122-e19d-4885-8b0f-dec7b686c6ea@o4g2000pra.googlegroups.com>
On Mon, Dec 22, 2008 at 6:24 PM, davetron5000 <davetron5000@gmail.com> wrote:
Show 25 quoted lines
> I have a repo on another disk that I ONLY use to backup my in-use
> local repo.  I have a post-commit hook that does the push (git push --
> all remote-repo-name)
>
>>git commit -a -m 'some change'
> Counting objects: 71, done.
> Compressing objects: 100% (26/26), done.
> Writing objects: 100% (29/29), 2.31 KiB, done.
> Total 29 (delta 12), reused 0 (delta 0)
> Unpacking objects: 100% (29/29), done.
> To file:///Volumes/Git/pose/main
>   22d7f10..0037aaf  bimonthly-frequency -> bimonthly-frequency
>  ! [rejected]        master -> master (non-fast forward)
> error: failed to push some refs to 'file:///Volumes/Git/pose/main'
> Created commit 0037aaf: Removed assertion that made no sense.
>  1 files changed, 0 insertions(+), 2 deletions(-)
>
> I'm using git as a front-end to Subversion, but I can't figure out why
> this is happening.
>
> The repo at /Volumes/Git/pose/main is NEVER pulled from or pushed to
> by anything other than my hook.  I can't understand why any push to it
> would NOT be a fast-forward.
>
> Any ideas how I can figure out what's going on?
Do you rebase your original repo?
-- 
Felipe Contreras
Previous: davetron5000Next: David Copeland
Message 2 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.