Hi Junio,
I just realised that my use-cases wouldn't be fully covered with the
onBranch configuration option.
On Fri, May 17, 2019 at 03:25:15AM -0400, Denton Liu wrote:
> Hi Junio,
>
> On Fri, May 17, 2019 at 01:12:04PM +0900, Junio C Hamano wrote:
> > Denton Liu writes:
> >
> > > diff --git
Hi Junio,
On Fri, May 17, 2019 at 01:12:04PM +0900, Junio C Hamano wrote:
> Denton Liu writes:
>
> > diff --git a/Documentation/config/format.txt
> > b/Documentation/config/format.txt
> > index dc77941c48..d387451573 100644
> > --- a/Documentation/config/format.txt
> > +++ b/Documentation/confi
Denton Liu writes:
> diff --git a/Documentation/config/format.txt b/Documentation/config/format.txt
> index dc77941c48..d387451573 100644
> --- a/Documentation/config/format.txt
> +++ b/Documentation/config/format.txt
> @@ -28,14 +28,22 @@ format.headers::
>
> format.to::
> format.cc::
> +for
Hi all,
I thought a lot about building the branch-specific include option but I
opted against this because `format..coverSubject` is a
branch-exclusive config option, whereas it doesn't make sense to have a
`format.coverSubject` option.
Thus, if we pursue this, we *need* to have a `format..*` sec
4 matches
Mail list logo