Git development
 help / color / mirror / Atom feed
From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: "R. Tyler Ballance" <tyler@slide.com>
Cc: git@vger.kernel.org
Subject: Re: Removing options from build
Date: Tue, 13 Jan 2009 22:55:50 +0100	[thread overview]
Message-ID: <20090113215550.GE30404@atjola.homenet> (raw)
In-Reply-To: <1231883002.14181.27.camel@starfruit>

On 2009.01.13 13:43:22 -0800, R. Tyler Ballance wrote:
> One of our developers "discovered" the --force option on `git push` and
> used it without taking the appropriate care and hosed one of the project
> branches we have running around in our central repository.
> 
> Besides a vigorous flogging, we're looking at other ways to prevent this
> sort of thing from happening again; the option we've settled on is to
> remove the "--force" flag from our internal build of v1.6.1
> 
> I'm wondering if somebody could point me in the right direction to
> remove "--force" (safely) from the builtin-push.c and removing the
> "rebase" command (we've got no use for it, and would prefer it gone).

git help config

receive.denyNonFastForwards (to refuse non-fast-forwards, even with -f)
receive.denyDeletes (to stop users from working around the non-ff using
                     a delete + recreate operation)

Björn

  parent reply	other threads:[~2009-01-13 21:57 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
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 [this message]
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=20090113215550.GE30404@atjola.homenet \
    --to=b.steinbrink@gmx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox