1git-reflog(1) 2============= 3 4NAME 5---- 6git-reflog - Manage reflog information 7 8 9SYNOPSIS 10-------- 11'git reflog' <subcommand> <options> 12 13DESCRIPTION 14----------- 15The command takes various subcommands, and different options 16depending on the subcommand: 17 18[verse] 19'git reflog expire' [--dry-run] [--stale-fix] [--verbose] 20 [--expire=<time>] [--expire-unreachable=<time>] [--all] <refs>... 21'git reflog delete' ref@\{specifier\}... 22'git reflog' ['show'] [log-options] [<ref>] 23 24Reflog is a mechanism to record when the tip of branches are 25updated. This command is to manage the information recorded in it. 26 27The subcommand "expire" is used to prune older reflog entries. 28Entries older than `expire` time, or entries older than 29`expire-unreachable` time and not reachable from the current 30tip, are removed from the reflog. This is typically not used 31directly by the end users -- instead, see linkgit:git-gc[1]. 32 33The subcommand "show" (which is also the default, in the absence of any 34subcommands) will take all the normal log options, and show the log of 35the reference provided in the command-line (or `HEAD`, by default). 36The reflog will cover all recent actions (HEAD reflog records branch switching 37as well). It is an alias for `git log -g --abbrev-commit --pretty=oneline`; 38see linkgit:git-log[1]. 39 40The reflog is useful in various git commands, to specify the old value 41of a reference. For example, `HEAD@\{2\}` means "where HEAD used to be 42two moves ago", `master@\{one.week.ago\}` means "where master used to 43point to one week ago", and so on. See linkgit:gitrevisions[7] for 44more details. 45 46To delete single entries from the reflog, use the subcommand "delete" 47and specify the _exact_ entry (e.g. "`git reflog delete master@\{2\}`"). 48 49 50OPTIONS 51------- 52 53--stale-fix:: 54 This revamps the logic -- the definition of "broken commit" 55 becomes: a commit that is not reachable from any of the refs and 56 there is a missing object among the commit, tree, or blob 57 objects reachable from it that is not reachable from any of the 58 refs. 59+ 60This computation involves traversing all the reachable objects, i.e. it 61has the same cost as 'git prune'. Fortunately, once this is run, we 62should not have to ever worry about missing objects, because the current 63prune and pack-objects know about reflogs and protect objects referred by 64them. 65 66--expire=<time>:: 67 Entries older than this time are pruned. Without the 68 option it is taken from configuration `gc.reflogExpire`, 69 which in turn defaults to 90 days. 70 71--expire-unreachable=<time>:: 72 Entries older than this time and not reachable from 73 the current tip of the branch are pruned. Without the 74 option it is taken from configuration 75 `gc.reflogExpireUnreachable`, which in turn defaults to 76 30 days. 77 78--all:: 79 Instead of listing <refs> explicitly, prune all refs. 80 81--updateref:: 82 Update the ref with the sha1 of the top reflog entry (i.e. 83 <ref>@\{0\}) after expiring or deleting. 84 85--rewrite:: 86 While expiring or deleting, adjust each reflog entry to ensure 87 that the `old` sha1 field points to the `new` sha1 field of the 88 previous entry. 89 90--verbose:: 91 Print extra information on screen. 92 93Author 94------ 95Written by Junio C Hamano <gitster@pobox.com> 96 97Documentation 98-------------- 99Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>. 100 101GIT 102--- 103Part of the linkgit:git[1] suite