Documentation / git-reflog.txton commit Allow fetch-pack to decide keeping the fetched pack without exploding (9e10fd1)
   1git-reflog(1)
   2=============
   3
   4NAME
   5----
   6git-reflog - Manage reflog information
   7
   8
   9SYNOPSIS
  10--------
  11[verse]
  12'git-reflog' expire [--dry-run] [--stale-fix]
  13        [--expire=<time>] [--expire-unreachable=<time>] [--all] <refs>...
  14
  15
  16DESCRIPTION
  17-----------
  18
  19Reflog is a mechanism to record when the tip of branches are
  20updated.  This command is to manage the information recorded in it.
  21
  22The subcommand "expire" is used to prune older reflog entries.
  23Entries older than `expire` time, or entries older than
  24`expire-unreachable` time and are not reachable from the current
  25tip, are removed from the reflog.  This is typically not used
  26directly by the end users -- instead, see gitlink:git-gc[1].
  27
  28
  29
  30OPTIONS
  31-------
  32
  33--expire=<time>::
  34        Entries older than this time are pruned.  Without the
  35        option it is taken from configuration `gc.reflogExpire`,
  36        which in turn defaults to 90 days.
  37
  38--expire-unreachable=<time>::
  39        Entries older than this time and are not reachable from
  40        the current tip of the branch are pruned.  Without the
  41        option it is taken from configuration
  42        `gc.reflogExpireUnreachable`, which in turn defaults to
  43        30 days.
  44
  45--all::
  46        Instead of listing <refs> explicitly, prune all refs.
  47
  48Author
  49------
  50Written by Junio C Hamano <junkio@cox.net>
  51
  52Documentation
  53--------------
  54Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
  55
  56GIT
  57---
  58Part of the gitlink:git[7] suite
  59