Subject: Re: [PATCH v3 3/3] revision: allow --ancestry-path to take an argument

From: Junio C Hamano <[email-masked]>
Date: Fri, 19 Aug 2022 10:54:30 -0700

"Elijah Newren via GitGitGadget" <[email-masked]> writes:

>  			ancestry_path:1,
> +
> +			/* True if --ancestry-path was specified without an
> +			 * argument. The bottom revisions are implicitly
> +			 * the arguments in this case.
> +			 */
> +			ancestry_path_implicit_bottoms:1,

The above comment explains why this is called "implicit" very well.
The earlier round used "need", but the word missed the essense (i.e.
ancestry_path argument is implicit and not given, so we need to
compute bottoms and use them instead).  The new name is certainly
better.