git-reflog(1) [debian man page]

GIT-REFLOG(1)							    Git Manual							     GIT-REFLOG(1)

NAME

       git-reflog - Manage reflog information

SYNOPSIS

       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>]

       Reflog is a mechanism to record when the tip of branches are updated. This command is to manage the information recorded in it.

       The subcommand "expire" is used to prune older reflog entries. Entries older than expire time, or entries older than expire-unreachable
       time and not reachable from the current tip, are removed from the reflog. This is typically not used directly by the end users -- instead,
       see git-gc(1).

       The subcommand "show" (which is also the default, in the absence of any subcommands) will take all the normal log options, and show the log
       of the reference provided in the command-line (or HEAD, by default). The reflog will cover all recent actions (HEAD reflog records branch
       switching as well). It is an alias for git log -g --abbrev-commit --pretty=oneline; see git-log(1).

       The reflog is useful in various git commands, to specify the old value of a reference. For example, HEAD@{2} means "where HEAD used to be
       two moves ago", master@{one.week.ago} means "where master used to point to one week ago", and so on. See gitrevisions(7) for more details.

       To delete single entries from the reflog, use the subcommand "delete" and specify the exact entry (e.g. "git reflog delete master@{2}").

OPTIONS

       --stale-fix
	   This 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-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.

       --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) suite

Git 1.7.10.4							    11/24/2012							     GIT-REFLOG(1)

Check Out this Related Man Page

GIT-PRUNE(1)                                                        Git Manual                                                        GIT-PRUNE(1)

NAME

       git-prune - Prune all unreachable objects from the object database

SYNOPSIS

       git prune [-n] [-v] [--progress] [--expire <time>] [--] [<head>...]

DESCRIPTION

           Note
           In most cases, users should run git gc, which calls git prune. See the section "NOTES", below.

       This runs git fsck --unreachable using all the refs available in refs/, optionally with additional set of objects specified on the command
       line, and prunes all unpacked objects unreachable from any of these head objects from the object database. In addition, it prunes the
       unpacked objects that are also found in packs by running git prune-packed. It also removes entries from .git/shallow that are not reachable
       by any ref.

       Note that unreachable, packed objects will remain. If this is not desired, see git-repack(1).

OPTIONS

       -n, --dry-run
           Do not remove anything; just report what it would remove.

       -v, --verbose
           Report all removed objects.

       --progress
           Show progress.

       --expire <time>
           Only expire loose objects older than <time>.

       --
           Do not interpret any more arguments as options.

       <head>...
           In addition to objects reachable from any of our references, keep objects reachable from listed <head>s.

EXAMPLE

       To prune objects not used by your repository or another that borrows from your repository via its .git/objects/info/alternates:

           $ git prune $(cd ../another && git rev-parse --all)

NOTES

       In most cases, users will not need to call git prune directly, but should instead call git gc, which handles pruning along with many other
       housekeeping tasks.

       For a description of which objects are considered for pruning, see git fsck's --unreachable option.

SEE ALSO

       git-fsck(1), git-gc(1), git-reflog(1)

GIT

       Part of the git(1) suite

Git 2.17.1                                                          10/05/2018                                                        GIT-PRUNE(1)

Linux and UNIX Man Pages

git-reflog(1) [debian man page]

Check Out this Related Man Page