Re: [PATCH] standardize usage strings that were missed the first time

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Junio C Hamano <gitster@xxxxxxxxx> writes:

> Alex Henrie <alexhenrie24@xxxxxxxxx> writes:
>
>> This is a follow-up to commit 9c9b4f2f8b7f27f3984e80d053106d5d41cbb03b.
>
> Please do not force the reader to type "git show 9c9b4f2".

Here is my attempt.

commit ce41720cad79d858f09ebfc88cf84a4b152645c7
Author: Alex Henrie <alexhenrie24@xxxxxxxxx>
Date:   Thu Apr 2 15:26:56 2015 -0600

    blame, log: format usage strings similarly to those in documentation
    
    Earlier, 9c9b4f2f (standardize usage info string format, 2015-01-13)
    tried to make usage-string in line with the documentation by
    
        - Placing angle brackets around fill-in-the-blank parameters
        - Putting dashes in multiword parameter names
        - Adding spaces to [-f|--foobar] to make [-f | --foobar]
        - Replacing <foobar>* with [<foobar>...]
    
    but it missed a few places.
    
    Signed-off-by: Alex Henrie <alexhenrie24@xxxxxxxxx>
    Signed-off-by: Junio C Hamano <gitster@xxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]