Re: git pull for update of netdev fails.

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Sep 20, 2006, 21:53 UTC
Message-ID: <Pine.LNX.4.63.0609202350160.19042@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <7vodtafc4g.fsf@assigned-by-dhcp.cox.net>

Hi,

On Wed, 20 Sep 2006, Junio C Hamano wrote:

Show 13 quoted lines

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> > I'd rather set another config variable with --shared, which tells git to 
> > refuse receiving non-fast-forwards. This could be a sensible setting in 
> > other setups than shared ones after all. Thoughts?
> 
> If this option is meant to forbid fixing up an screw-up by doing
> "git-push --force", I do not quite like it.
> 
> It sounds as if arguing that "rm -fr" is dangerous so presence
> of -f and -r at the same time should imply -i option.  I think
> the right answer is not making -i implied, but train the user to
> understand what -fr means before using it.

I think it is more like being nice, and disallowing "rm -rf" via FTP, forcing the user to do it locally.

In a shared repository I really, really, I mean: really, do not want to mess a branch up that others pull from. And if I have to fix something, I _can_ do it locally. (Plus the hassle reminds me of giving the pullers a heads-up.)

Ciao, Dscho