On Feb 9, 2008, at 4:00 AM, Jeff King wrote:

quoted text
>
> I really think that Steffen's "default to pushing only the current
> branch" approach fits much better with the model described in your
> workflow, and is generally a safer default. IIRC, the main  
> objection was
> that old-timers like the current push behavior better. Steffen, was
> there objection to a "push.onlyHEAD" config option?

There might have been an argument like: We should have a single
default because otherwise the behaviour of git depends on the
local configuration of the user.  This may cause even more
confusion than it tries to solve, because now you always need
to start first talking about the local configuration of the
users before you can start explaining how to actually solve the
problem.

Personally, I decided it is safer to teach users to explicitly
type what they mean.  I'd probably not use the push.onlyHEAD
config option.

I also proposed that the default could do nothing if no explicit
push lines are in the configuration file.  Users would be forced
to explicitly type what the want: Either they can say "--matching"
or they can say "--current".  This is similar to the new
"git clean" default.  But I remember there *was* objection against
this because everyone would be forced to type more and different
than "git clean" the default of "git push" is considered "safe",
so there's no need to protect the user from "git push".

Junio proposed various possible changes to the configuration
variables that could resolve the issues.  I do not remember the
details.

	Steffen
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html