Re: [PATCH v8 4/7] git-reflog: add exists command

[Michael Haggerty <mhagger@alum.mit.edu>]

On 07/09/2015 03:50 PM, David Turner wrote:
> Theis are necessary because alternate ref backends might store reflogs
> somewhere other than .git/logs.  Code that now directly manipulates
> .git/logs should instead go through git-reflog.
> 
> Signed-off-by: David Turner <dturner@twopensource.com>
> ---
>  Documentation/git-reflog.txt |  4 ++++
>  builtin/reflog.c             | 33 ++++++++++++++++++++++++++++++++-
>  t/t1411-reflog-show.sh       |  5 +++++
>  3 files changed, 41 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/git-reflog.txt b/Documentation/git-reflog.txt
> index 5e7908e..4b08fc7 100644
> --- a/Documentation/git-reflog.txt
> +++ b/Documentation/git-reflog.txt
> @@ -23,6 +23,7 @@ depending on the subcommand:
>  	[--dry-run] [--verbose] [--all | <refs>...]
>  'git reflog delete' [--rewrite] [--updateref]
>  	[--dry-run] [--verbose] ref@\{specifier\}...
> +'git reflog exists' <ref>
>  
>  Reference logs, or "reflogs", record when the tips of branches and
>  other references were updated in the local repository. Reflogs are
> @@ -52,6 +53,9 @@ argument must be an _exact_ entry (e.g. "`git reflog delete
>  master@{2}`"). This subcommand is also typically not used directly by
>  end users.
>  
> +The "exists" subcommand checks whether a ref has a reflog.  It exists

The second "exists" should be "exits".

> +with zero status if the reflog exists, and non-zero status if it does
> +not.
>  
> [...]

Michael

-- 
Michael Haggerty
mhagger@alum.mit.edu