table of contents
other versions
- jessie 1:2.1.4-2.1+deb8u6
- jessie-backports 1:2.11.0-3~bpo8+1
- stretch 1:2.11.0-3+deb9u4
- testing 1:2.20.1-2
- stretch-backports 1:2.20.1-1~bpo9+1
- unstable 1:2.20.1-2
- experimental 1:2.21.0+next.20190320-1
GIT-REFLOG(1) | Git Manual | GIT-REFLOG(1) |
NAME¶
git-reflog - Manage reflog informationSYNOPSIS¶
git reflog <subcommand> <options>
DESCRIPTION¶
The command takes various subcommands, and different options depending on the subcommand:git reflog expire [--dry-run] [--stale-fix] [--verbose] [--expire=<time>] [--expire-unreachable=<time>] [--all] <refs>... git reflog delete ref@{specifier}... git reflog [show] [log-options] [<ref>]
OPTIONS¶
--stale-fixThis revamps the logic — the definition of
"broken commit" becomes: a commit that is not reachable from any of
the refs and there is a missing object among the commit, tree, or blob objects
reachable from it that is not reachable from any of the refs.
This computation involves traversing all the reachable objects, i.e. it has the
same cost as git prune. Fortunately, once this is run, we should not
have to ever worry about missing objects, because the current prune and
pack-objects know about reflogs and protect objects referred by them.
--expire=<time>
Entries older than this time are pruned. Without the
option it is taken from configuration gc.reflogExpire, which in turn defaults
to 90 days. --expire=all prunes entries regardless of their age;
--expire=never turns off pruning of reachable entries (but see
--expire-unreachable).
--expire-unreachable=<time>
Entries older than this time and not reachable from the
current tip of the branch are pruned. Without the option it is taken from
configuration gc.reflogExpireUnreachable, which in turn defaults to 30 days.
--expire-unreachable=all prunes unreachable entries regardless of their age;
--expire-unreachable=never turns off early pruning of unreachable entries (but
see --expire).
--all
Instead of listing <refs> explicitly, prune all
refs.
--updateref
Update the ref with the sha1 of the top reflog entry
(i.e. <ref>@{0}) after expiring or deleting.
--rewrite
While expiring or deleting, adjust each reflog entry to
ensure that the old sha1 field points to the new sha1 field of the previous
entry.
--verbose
Print extra information on screen.
GIT¶
Part of the git(1) suite05/28/2018 | Git 2.1.4 |