Re: disallowing push to currently checked-out branch

On Sun, Feb 15, 2009 at 05:33:59PM -0800, david@lang.hm wrote:

quoted

It is already implemented; the proposal is about setting the default.
The plans for 1.6.2 are already to issue a warning and ask the user to
set the config variable to shut it up.

if this is going to be done the timeframe for making the change should be  

I don't know that a particular timeframe for switching the default has
been chosen at this point. There is a short warning in 1.6.1, and a much
more comprehensive warning will be in 1.6.2 (which should be released
shortly).

quite long. think in terms of debian stable or RHEL, whatever version they 
ship is what their users are going to use. it doesn't matter how many new  
versions and what warnings you have the produce in the meantime, the users 
won't see them.

Sadly, Debian 5.0 just shipped with git 1.5.6.5, which has no warning
(and dashed commands!).

note that this isn't always stupid to do, if you are deploying them on a  
network with no Internet access the stability of knowing that things are  
_exactly_ what you tested may be worth more than updates that close bugs  
that you don't hit or add features that you aren't using (or introduce  
unexpected changes like spitting warnings or errors for things that the  
old version didn't, which is exactly what is being proposed.

I'm not sure I understand your argument here. If you have a machine that
needs to do _exactly_ what you have tested, then wouldn't you be
concerned about upgrading git 1.5.6.5 to (for example) git 1.7? Or since
you are probably looking at a more macro-level, upgrading Debian 5.0 to
Debian 6.0?

-Peff