> -----Original Message----- > From: git-owner@xxxxxxxxxxxxxxx [mailto:git-owner@xxxxxxxxxxxxxxx] On > Behalf Of Nathan W. Panike > Sent: den 21 maj 2010 15:26 > To: git@xxxxxxxxxxxxxxx > Subject: [PATCH RFC] Add a config verbose option fetch and push > > --- > There are a couple projects that I follow where I find it useful to always > set the verbose flag. Setting this in the configuration file would let me > avoid the times I forget to set it on the command line. I decided to do both > push and fetch at the same time. > > Documentation/config.txt | 10 ++++++++++ > builtin/fetch.c | 7 +++++++ > builtin/push.c | 7 +++++++ > 3 files changed, 24 insertions(+), 0 deletions(-) > > diff --git a/Documentation/config.txt b/Documentation/config.txt > index 39140ba..8e8a760 100644 > --- a/Documentation/config.txt > +++ b/Documentation/config.txt > @@ -860,6 +860,11 @@ fetch.unpackLimit:: > especially on slow filesystems. If not set, the value of > `transfer.unpackLimit` is used instead. > > +fetch.verbose:: > + If true, it is the same as setting "-v" on the command line. If it is > + false or not defined, git will use the command line parameters to > + decide the verboseness of fetch. > + Don't you usually use the configured option as the default, and then let the command line options override it (e.g., by specifying --no-verbose). //Peter -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html