Re: Missing git options

From: Martin Häcker <mhaecker@schwarz-online.org>
Date: Feb 6, 2018, 11:13 UTC
Message-ID: <C6AF93BC-048F-4944-AB87-36AC2A5C5466@schwarz-online.org>
In-Reply-To: <20180206004313.GC7904@genre.crustytoothpaste.net>

Hi all,

Show 7 quoted lines

> 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