Thread (7 messages) flat view 7 messages, 6 authors, 2018-02-06

Re: Missing git options

From: Martin Häcker <hidden>
Date: 2018-02-06 11:13:20

Hi all,
Am 06.02.2018 um 01:43 schrieb brian m. carlson [off-list ref]:

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

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help