From: "Felipe Contreras" <felipe.contreras@gmail.com>
To: "David Copeland" <davetron5000@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: push to backup repo periodically fails with "not fast forward"
Date: Mon, 22 Dec 2008 19:19:26 +0200 [thread overview]
Message-ID: <94a0d4530812220919t25233fa9ub461c86f10ec366d@mail.gmail.com> (raw)
In-Reply-To: <f95d47890812220915h5286d2bdv7c8412ecf77be999@mail.gmail.com>
On Mon, Dec 22, 2008 at 7:15 PM, David Copeland <davetron5000@gmail.com> wrote:
> 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
next prev parent reply other threads:[~2008-12-22 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 16:24 push to backup repo periodically fails with "not fast forward" davetron5000
2008-12-22 17:11 ` Felipe Contreras
2008-12-22 17:15 ` David Copeland
2008-12-22 17:19 ` Felipe Contreras [this message]
2008-12-22 18:27 ` Nicolas Pitre
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=94a0d4530812220919t25233fa9ub461c86f10ec366d@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=davetron5000@gmail.com \
--cc=git@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox