From: Jonathan Nieder <jrnieder@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Will Palmer <wmpalmer@gmail.com>,
git@vger.kernel.org, gitster@pobox.com,
Cheng Renquan <crquan@gmail.com>
Subject: Re: [PATCH 0/3] pretty: format aliases
Date: Sun, 25 Apr 2010 17:09:55 -0500 [thread overview]
Message-ID: <20100425220955.GA25620@progeny.tock> (raw)
In-Reply-To: <20100425194800.GB14736@coredump.intra.peff.net>
Jeff King wrote:
> The config variables format.* are traditionally about format-patch. I
> see we have format.pretty these days, too.
Yes, it as added in commit v1.5.5-rc0~57^2 (log/show/whatchanged:
introduce format.pretty configuration, 2008-03-02):
When running log/show/whatchanged from the command line, the user may want
to use a preferred format without having to pass --pretty=<fmt> option
every time from the command line. This teaches these three commands to
honor a new configuration variable, format.pretty.
The --pretty option given from the command line will override the
configured format.
I use it to mess with line wrapping; that it’s possible is very nice.
Thanks, Renquan.
Jonathan
next prev parent reply other threads:[~2010-04-25 22:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-25 15:42 [PATCH 0/3] pretty: format aliases Will Palmer
2010-04-25 15:42 ` [PATCH 1/3] pretty: add conditional %C?colorname placeholders Will Palmer
2010-04-26 6:30 ` Alex Riesen
[not found] ` <r2o5b9751661004260113m7b6c387bm8467a063c13e5a0f@mail.gmail.com>
2010-04-26 8:20 ` Will Palmer
2010-04-25 15:42 ` [PATCH 2/3] pretty: make %H/%h dependent on --abbrev[-commit] Will Palmer
2010-04-25 15:42 ` [PATCH 3/3] pretty: add aliases for pretty formats Will Palmer
2010-04-25 19:48 ` [PATCH 0/3] pretty: format aliases Jeff King
2010-04-25 20:40 ` Will Palmer
2010-04-25 22:09 ` Jonathan Nieder [this message]
2010-04-26 17:22 ` Jeff King
2010-04-26 17:57 ` Jonathan Nieder
2010-04-26 18:07 ` Jeff King
2010-04-26 18:37 ` Jonathan Nieder
2010-04-26 21:14 ` Will Palmer
2010-04-26 22:00 ` Jonathan Nieder
2010-04-27 1:25 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100425220955.GA25620@progeny.tock \
--to=jrnieder@gmail.com \
--cc=crquan@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=wmpalmer@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).