From: Wesley Schwengle <wesley@schwengle.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, me@ttaylorr.com
Subject: Re: Possible git bug
Date: Thu, 16 Sep 2021 18:30:46 -0400 [thread overview]
Message-ID: <4d17d26a-d945-3875-beed-e23ae6281f54@schwengle.net> (raw)
In-Reply-To: <xmqqmtocrxwq.fsf@gitster.g>
On 9/16/21 5:52 PM, Junio C Hamano wrote:
> Wesley Schwengle <wesley@schwengle.net> writes:
>> As for the patch. The reason why --fork-point is default I do not
>> know, but how to disable it isn't documented and I think it should. It
>> is hidden in the source code and the release notes of 2.31.0. It
>> should be more visible. Which is the reason I submitted the patch.
>
> Certainly.
>
> In any case, updating the documentation to refer to the configuraion
> variable that tweaks the default for --fork-point would be a good
> near-term thing to do, but in the longer term, I think it may make
> sense to fix this "surprise" and transition the default over time,
> i.e.
>
> "git config --help" is the only end-user facing place the reference
> from the configuration variable to the command line option is found.
> We should also have a backreference from the command line option to
> the configuration variable.
A simple reference in the documentation would be a good first step and
the change of the default can than happen over multiple iterations/versions.
Cheers,
Wesley
--
Wesley Schwengle
E: wesley@schwengle.net
next prev parent reply other threads:[~2021-09-16 22:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 3:29 Possible git bug Wesley Schwengle
2021-09-16 5:37 ` Taylor Blau
2021-09-16 12:07 ` Wesley Schwengle
2021-09-16 12:47 ` wesley
2021-09-16 12:47 ` [PATCH] Document `rebase.forkpoint` in rebase man page wesley
2021-09-16 15:43 ` Junio C Hamano
2021-09-16 21:21 ` Junio C Hamano
2021-09-16 22:35 ` Possible git bug wesley
2021-09-16 22:35 ` [PATCH] Document `rebase.forkpoint` in rebase man page wesley
2021-09-16 22:47 ` Junio C Hamano
2021-09-16 22:50 ` Wesley Schwengle
2021-09-16 22:53 ` Junio C Hamano
2021-09-20 14:34 ` Wesley Schwengle
2021-09-16 22:46 ` Possible git bug wesley
2021-09-16 22:46 ` [PATCH] Document `rebase.forkpoint` in rebase man page wesley
2021-09-20 16:07 ` Junio C Hamano
2021-09-16 15:33 ` Possible git bug Junio C Hamano
2021-09-16 19:39 ` Wesley Schwengle
2021-09-16 21:52 ` Junio C Hamano
2021-09-16 22:30 ` Wesley Schwengle [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-14 4:50 Hugh Davenport
2013-08-14 5:42 ` Daniel Knittl-Frank
2013-08-14 6:53 ` Jeff King
2009-01-17 13:52 Damon LaCrosse
2009-01-17 15:16 ` Johannes Schindelin
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=4d17d26a-d945-3875-beed-e23ae6281f54@schwengle.net \
--to=wesley@schwengle.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.com \
/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).