From: Junio C Hamano Date: Wed, 21 Sep 2011 02:44:50 GMT Subject: Re: [PATCH 2/3] branch: teach --edit-description option Message-ID: <7v7h524nrx.fsf@alter.siamese.dyndns.org> In-Reply-To: Andrew Ardill writes: > I understand your reasoning here, however is there a way to allow > setting the branch description in, for example, a script? As you read in the patch, especially the documentation part, there is not a way to do that. I am not interested because it does not directly help my cause of helping the human communication between the kernel developers who may want to perform a signed push to their public repository and send their pull requests with the same message to Linus. That does _not_ mean I will _reject_ a patch to add such a feature. It just means writing such a patch myself or reviewing and accepting such a patch is not very high in my prioritized list at this point in the evolution of the series. Teaching the use of the information to other commands such as "format-patch --cover-letter" would have much higher precedence. > Additionally I can imagine it would be useful to be able to set the > branch description from another tool, what is the recommended way of > doing that? Should tools modify the config directly?? An obvious answer: "do whatever you want". The only rule that the programs that need to follow is that branch.$name.description has the string to use to obtain the explanation text. How they achieve that (perhaps by running "git config") is of secondary importance.