Øystein Walle <oystwa@xxxxxxxxx> writes:
> Sort of... I think I meant s/printed it/printed/ :-)
>
>> "git tag" is mentioned in the subject line, but not here.
>
> It should definitely be added, yes. Junio, should I resend or will you touch up
> the message? Not sure what the proper procedure is since it's already in seen.
As I write in "What's cooking", being in 'seen' does not count all
that much and we can freely replace them and erace the trace of
"past mistakes", until the series hits 'next'. For small changes
like this, telling me to touch them up, as long as the necessary
changes are obvious, is just fine. Sending out v4 is also fine for
a series of any size.
I just locally amended the commit log message.
Thanks.
1: e0053ad012 ! 1: aabfdc9514 branch, for-each-ref, tag: add option to omit empty lines
@@ Metadata
## Commit message ##
branch, for-each-ref, tag: add option to omit empty lines
- If the given format string expands to the empty string a newline is
- still printed it. This makes using the output linewise more tedious. For
+ If the given format string expands to the empty string, a newline is
+ still printed. This makes using the output linewise more tedious. For
example, git update-ref --stdin does not accept empty lines.
- Add options to branch and for-each-ref to not print these empty lines.
- The default behavior remains the same.
+ Add options to "git branch", "git for-each-ref", and "git tag" to
+ not print these empty lines. The default behavior remains the same.
Signed-off-by: Øystein Walle <oystwa@xxxxxxxxx>
Signed-off-by: Junio C Hamano <gitster@xxxxxxxxx>
