From: "Martin Häcker" <mhaecker@schwarz-online.org>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org
Subject: Re: Missing git options
Date: Tue, 6 Feb 2018 12:13:12 +0100 [thread overview]
Message-ID: <C6AF93BC-048F-4944-AB87-36AC2A5C5466@schwarz-online.org> (raw)
In-Reply-To: <20180206004313.GC7904@genre.crustytoothpaste.net>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
Hi all,
> Am 06.02.2018 um 01:43 schrieb brian m. carlson <sandals@crustytoothpaste.net>:
>
> 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.
While I share your concern, this is something that will completely freeze development of the git tui which I cannot imagine is wanted.
If this where my tool, I would much rather advertise an output format specifically for scripting.
An interim solution could be something like an `—ignore-configuration` option that allows script writers to get predictable output. This however still freezes the default output of git forever.
So you will need something like —output-for=scripting|json|xml|whatever sooner or later. Mixing up the TUI for humans and for scripts is not going to be fun to evolve.
Best Regards,
Martin Häcker
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 235 bytes --]
next prev parent reply other threads:[~2018-02-06 11:13 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
2018-02-06 11:13 ` Martin Häcker [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C6AF93BC-048F-4944-AB87-36AC2A5C5466@schwarz-online.org \
--to=mhaecker@schwarz-online.org \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).