On Tue, Sep 1, 2015 at 10:50 AM, Barry Warsaw <ba...@python.org> wrote: > On Sep 01, 2015, at 09:42 AM, Junio C Hamano wrote: > >>That way, you are forcing all the existing scripts to be updated to >>say "git -c ..." for _all_ invocations of Git they have, aren't you? > > No, why? If the default value enables the current ui, then no scripts need > changing. Users can enable the new ui for their own benefit at their own > pace. If you eventually want to make the new ui the default, provide a > sufficient transition period. > > Cheers, > -Barry
So say I am a user who wants to take the new command set. And as I am lazy to type it all the time I just do: $ git config --global command-version 2 Now I have all the new fancy stuff when I type it directly into the terminal. But when I run one of the old scripts my coworker gave me (which is used to the old notion), it must adhere to the old command world. How do you now figure out if this is interactive or script? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
