Thanks for clarification. I will update the patch and re-send it. Tigran.
----- Original Message ----- > From: "Junio C Hamano" <[email protected]> > To: "Tigran Mkrtchyan" <[email protected]> > Cc: "git" <[email protected]>, "Jonathan Nieder" <[email protected]>, > "Johannes Schindelin" > <[email protected]> > Sent: Wednesday, June 5, 2019 10:46:05 PM > Subject: Re: [PATCH v3] tag: add tag.gpgSign config option to force all tags > be GPG-signed > "Mkrtchyan, Tigran" <[email protected]> writes: > >>> But more importantly, I think we should justify why this "not >>> allowed" makes sense as the design of the feature. A plausible >>> alternative design would simply follow the "last one wins" paradigm, >>> ... >> This is matter of convention. > > Oh, if you put it that way, it is quite clear that we should redo > this part, as the rest of Git command line processing all pretty > much follow "last one wins". I was mostly curious if there was any > strong reason why this combination has to be different.
