On Thu, Feb 19, 2015 at 5:32 PM, Matthieu Moy <Matthieu.Moy@xxxxxxxxxxxxxxx> wrote: > +### Add configuration options for some commonly used command-line options > + > +This includes: > + > +* git am -3 > + > +* git am -c > + > +Some people always run the command with these options, and would > +prefer to be able to activate them by default in ~/.gitconfig. I was reading the .md file to add a new microproject and found this. Instead of adding new config case by case, should we do something more generic? We could have a new group defaultOptions.<command> (or <command>.options) which contains <option-name> = <value> where option names are the long name in parse-options? Then we don't have to manually add more config options any more (mostly, I'm aware of stuff like diff options that do not use parse-options). If we want to stop the users from shooting themselves in the foot, we could extend parse-options to allow/disallow certain options being used this way. Hmm? -- Duy