LinuxGuruz
  • Last 5 Forum Topics
    Replies
    Views
    Last post


The Web Only This Site
  • BOOKMARK

  • ADD TO FAVORITES

  • REFERENCES


  • MARC

    Mailing list ARChives
    - Search by -
     Subjects
     Authors
     Bodies





    FOLDOC

    Computing Dictionary




  • Text Link Ads






  • LINUX man pages
  • Linux Man Page Viewer


    The following form allows you to view linux man pages.

    Command:

    git-reflog

    
    
    

    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 git-rev-parse(1) 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
               <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.
    
    
    

    AUTHOR

           Written by Junio C Hamano <gitster@pobox.com[1]>
    
    
    

    DOCUMENTATION

           Documentation by Junio C Hamano and the git-list
           <git@vger.kernel.org[2]>.
    
    
    

    GIT

           Part of the git(1) suite
    
    
    

    NOTES

            1. gitster@pobox.com
               mailto:gitster@pobox.com
    
            2. git@vger.kernel.org
               mailto:git@vger.kernel.org
    
    
    

    Git 1.7.1 03/04/2013 GIT-REFLOG(1)

    
    
  • MORE RESOURCE


  • Linux

    The Distributions





    Linux

    The Software





    Linux

    The News



  • MARKETING






  • Toll Free

webmaster@linuxguruz.com
Copyright © 1999 - 2016 by LinuxGuruz