Martin Langhoff [off-list ref] writes:
--force should change behaviour, immediately, to "current" or even none
(forcing the user to name the remote and branch explicitly).
Any "immediately" change is never going to happen merely based on "I
cannot imagine in what use case it is useful".
As many people already said in the discussion before the RFD message that
is at the root of this thread, the name of the option --force alone
already signals it is something you use after thinking twice.
On Tue, Mar 20, 2012 at 11:28 AM, Junio C Hamano [off-list ref] wrote:
As many people already said in the discussion before the RFD message that
is at the root of this thread, the name of the option --force alone
already signals it is something you use after thinking twice.
Definitely. You may think twice about the branch you' re planning to
force-update. "Do I really want to force-update <this>?". But it
doesn't mean you know and fully understand the "push default" rules of
git.
With "immediately" I mean "sooner than several releases away".
In any case, seems I missed the train and the discussion is closed;
I'll head back to my cave.
cheers,
m
--
martin.langhoff@gmail.com
martin@laptop.org -- Software Architect - OLPC
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff