From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Martin Häcker" <mhaecker@schwarz-online.org>
Cc: git@vger.kernel.org
Subject: Re: Missing git options
Date: Tue, 6 Feb 2018 00:43:13 +0000 [thread overview]
Message-ID: <20180206004313.GC7904@genre.crustytoothpaste.net> (raw)
In-Reply-To: <AD196D8E-04DB-4274-ADEB-D914A79628B3@schwarz-online.org>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
On Mon, Feb 05, 2018 at 10:12:05AM +0100, Martin Häcker wrote:
> Hi there,
>
> I just recently learned that not all command line switches seem to automatically correlate to options in the git configuration.
>
> This seems something that should be relatively easy to fix.
>
> What I’m most missing is
>
> — snip —
> [log]
> graph = true
> patch = true
> — snap —
>
> which would / should correspond to `git log —graph —patch`.
>
> What do you guys think?
I think this is likely to cause problems. Many people use git log with
--pretty to format commit hashes or messages into other programs. I'm
aware of multiple tools that will simply break if --graph or --patch
become the default. Requiring people to retrofit their tools to use
--no-graph or --no-patch is likely to be a burden.
--
brian m. carlson / brian with sandals: Houston, Texas, US
https://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 867 bytes --]
next prev parent reply other threads:[~2018-02-06 0:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 9:12 Missing git options Martin Häcker
2018-02-05 18:56 ` Stefan Beller
2018-02-05 19:41 ` Junio C Hamano
2018-02-05 20:11 ` Ævar Arnfjörð Bjarmason
2018-02-06 0:43 ` brian m. carlson [this message]
2018-02-06 11:13 ` Martin Häcker
2018-02-06 11:47 ` Duy Nguyen
2018-02-06 18:27 ` Jonathan Nieder
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=20180206004313.GC7904@genre.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=mhaecker@schwarz-online.org \
/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).