From: Thomas Rast <trast@student.ethz.ch>
To: "R. Tyler Ballance" <tyler@slide.com>
Cc: git@vger.kernel.org
Subject: Re: Removing options from build
Date: Tue, 13 Jan 2009 22:56:36 +0100 [thread overview]
Message-ID: <200901132256.40313.trast@student.ethz.ch> (raw)
In-Reply-To: <200901132253.15370.trast@student.ethz.ch>
[-- Attachment #1: Type: text/plain, Size: 701 bytes --]
Thomas Rast wrote:
> R. Tyler Ballance wrote:
> > I'm wondering if somebody could point me in the right direction to
> > remove "--force" (safely) from the builtin-push.c
>
> IMHO your update (or pre-receive) hook should just disallow
> non-fast-forward updates.
Actually there's even this config option:
receive.denyNonFastForwards
If set to true, git-receive-pack will deny a ref update
which is not a fast forward. Use this to prevent such an
update via a push, even if that push is forced. This
configuration variable is set when initializing a shared
repository.
--
Thomas Rast
trast@{inf,student}.ethz.ch
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-13 21:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 21:43 Removing options from build R. Tyler Ballance
2009-01-13 21:53 ` Thomas Rast
2009-01-13 21:56 ` Thomas Rast [this message]
2009-01-13 22:00 ` R. Tyler Ballance
2009-01-13 22:07 ` Björn Steinbrink
2009-01-13 22:10 ` Boyd Stephen Smith Jr.
2009-01-13 22:47 ` Daniel Barkalow
2009-01-13 21:55 ` Björn Steinbrink
2009-01-13 22:05 ` Jakub Narebski
2009-01-13 22:06 ` Boyd Stephen Smith Jr.
2009-01-13 22:18 ` R. Tyler Ballance
2009-01-13 22:34 ` Boyd Stephen Smith Jr.
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=200901132256.40313.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=tyler@slide.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.