From: Alex Henrie <alexhenrie24@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git mailing list <git@vger.kernel.org>, paulus@ozlabs.org
Subject: Re: [PATCH v3 4/4] gitk: pass --no-graph to `git log`
Date: Fri, 11 Feb 2022 13:08:26 -0700 [thread overview]
Message-ID: <CAMMLpeTWvN45jTmoFHBS2+E+wEuBKTAnxXh3+RWzJc0O2rYy2A@mail.gmail.com> (raw)
In-Reply-To: <xmqq5yplb46m.fsf@gitster.g>
On Fri, Feb 11, 2022 at 12:20 PM Junio C Hamano <gitster@pobox.com> wrote:
>
> Alex Henrie <alexhenrie24@gmail.com> writes:
>
> > What if we make log.graph=true also require feature.experimental=true?
>
> No. feature.experimental is to give people an opt-in opportunity
> for features that we are considering to enable by default.
>
> > The log.graph option would really be a useful feature for people who
> > use Git exclusively from the CLI without any external tools. It seems
> > that the main challenge is how to give others time to adjust.
>
> Those who want to see log by default must need to twaek their
> configuration. Instead of doing "git config log.graph true" and
> breaking tools, they can do "git config alias.mylog 'log --graph'"
> with the same ease, without breaking anything.
>
> So...
Yeah, that's not a bad solution. I actually have `git graph` aliased to
`git log --graph --abbrev-commit --pretty=oneline` for this purpose.
If a lot of people are doing that, maybe a new command should be added
to Git itself. It seems like there's not much demand for that at the
moment though.
-Alex
next prev parent reply other threads:[~2022-02-11 20:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 16:36 [PATCH v3 1/4] log: fix memory leak if --graph is passed multiple times Alex Henrie
2022-02-11 16:36 ` [PATCH v3 2/4] log: add a --no-graph option Alex Henrie
2022-02-11 19:02 ` Junio C Hamano
2022-02-11 19:20 ` Alex Henrie
2022-02-11 16:36 ` [PATCH v3 3/4] log: add a log.graph config option Alex Henrie
2022-02-11 16:36 ` [PATCH v3 4/4] gitk: pass --no-graph to `git log` Alex Henrie
2022-02-11 18:12 ` Junio C Hamano
2022-02-11 19:05 ` Alex Henrie
2022-02-11 19:20 ` Junio C Hamano
2022-02-11 20:00 ` Junio C Hamano
2022-02-11 20:11 ` Alex Henrie
2022-02-11 20:08 ` Alex Henrie [this message]
2022-02-11 18:51 ` [PATCH v3 1/4] log: fix memory leak if --graph is passed multiple times Junio C Hamano
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=CAMMLpeTWvN45jTmoFHBS2+E+wEuBKTAnxXh3+RWzJc0O2rYy2A@mail.gmail.com \
--to=alexhenrie24@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=paulus@ozlabs.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.
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).