Re: disallowing push to currently checked-out branch

Hi,

On Mon, 16 Feb 2009, Jeff King wrote:

On Sun, Feb 15, 2009 at 09:55:24PM -0800, david@lang.hm wrote:

quoted

two cycles of changes, not three, so 6-10 years for changes that break 
existing bahavior without a _really_ pressing reason. so new 
functions, new commands, new flags don't have to wait at all. it's 
only if you want to change something that will cause grief for users 
if they get a new version and run their existing tools against it.

I think you have to think about _how much_ grief it will cause, too.

Exactly.

BTW I already get angry questions by Git users why this bug -- as they 
think about it -- is not fixed in the next Git release, and I patiently 
explain that a lot of existing users would get hurt by that change.

And on this list I get flak when pushing for Git users' needs (who will 
never be subscribed to the Git list because of the sheer volume).

I guess if both camps would just start to think a little bit about the 
other camp's needs, everybody would get a little calmer.

Ciao,
Dscho