Re: [PATCH v4 0/9] Allow overriding the default name of the default branch

From: Edward Thomson <ethomson@edwardthomson.com>
Date: Jul 12, 2020, 13:03 UTC
Message-ID: <CA+WKDT2DV6ymu-AG9B2h34=K+4KW7tcCpAfTV-rTdifqfS7R=g@mail.gmail.com>
In-Reply-To: <20200629224113.GC9782@camp.crustytoothpaste.net>

On Mon, Jun 29, 2020 at 11:42 PM brian m. carlson <sandals@crustytoothpaste.net> wrote:

Show 7 quoted lines

>
> I'm very happy with this and the way it's progressed since v1.  This
> seems simpler than earlier designs, and I appreciate the improved focus
> on avoiding special-casing branches, since I think that will make it
> easier for folks to choose branch naming that suits them.
>
> Thanks for working on this.

I agree, this is an improvement.

One thing that isn't obvious to me, though, is why templates take precedence over the command-line option. I would expect the command-line option to be the highest priority option given, just like configuration values specified on the command-line override values from configuration files.

Cheers- -ed