Re: [PATCH 0/7] teach branch-specific options for format-patch
- Date: Tue, 07 May 2019 17:56:00 +0900
- From: Junio C Hamano <gitster@xxxxxxxxx>
- Subject: Re: [PATCH 0/7] teach branch-specific options for format-patch
Denton Liu <liu.denton@xxxxxxxxx> writes:
> Currently, format-patch only accepts branch.<name>.description as a
> branch-specific configuration variable. However, there are many other
> options which would be useful to have on a branch-by-branch basis,
> namely cover letter subject and To: and Cc: headers.
> Teach format-patch to recognise these branch-specific configuration
> Note that this patchset was created using these new configuration
> [branch "submitted/fix-revisions-txt"]
> coverSubject = "cleanup revisions.txt"
> cc = "Andreas Heiduk <asheiduk@xxxxxxxxx>"
> cc = "Duy Nguyen <pclouds@xxxxxxxxx>"
> cc = "Junio C Hamano <gitster@xxxxxxxxx>"
Do we have format.<something> configuration for these things?
What I am trying to get at is if these are better structured similar
to http options where http.<something> supplies the overall default
for <something>, while http.<destination>.<something> gives a more
destination site specific override of that default. I.e. format.cc
is used as fallback, while format.<branch>.cc is used to override.
In any case, it smells to me that branch.<branch>.cc does not hint
strongly enough that they are meant to affect format-patch.