From: Junio C Hamano <junkio@cox.net>
To: Sylvain Beucler <beuc@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: Overwriting bare repositories' master
Date: Sun, 29 Oct 2006 14:05:35 -0800 [thread overview]
Message-ID: <7vlkmyzsk0.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20061029215758.GA24385@localhost.localdomain> (Sylvain Beucler's message of "Sun, 29 Oct 2006 22:57:58 +0100")
Sylvain Beucler <beuc@gnu.org> writes:
> ShadeHawk at #git noticed that this does not apply for a local
> directory.
Do not top-post please.
> I reproduced the two successive push-es both to a local git
> repository, and then to a remote git-shell'd one, and indeed, it works
> locally but it is rejected remotely ("error: denying non-fast forward;
> you should pull first").
>
> So this is probably caused by git-shell restrictions.
I do not think so. Have you checked your config to see if you
have receive.denyNonFastforwards set?
I suspect Jakub (ShadeHawk)'s test does not have it.
next prev parent reply other threads:[~2006-10-29 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 21:03 Overwriting bare repositories' master Sylvain Beucler
2006-10-29 21:57 ` Sylvain Beucler
2006-10-29 22:05 ` Junio C Hamano [this message]
2006-10-29 21:59 ` Junio C Hamano
2006-10-29 22:21 ` Sylvain Beucler
2006-10-29 22:43 ` Johannes Schindelin
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=7vlkmyzsk0.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=beuc@gnu.org \
--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