1GIT-RESTORE-MTIME(1)        General Commands Manual       GIT-RESTORE-MTIME(1)
2
3
4

NAME

6       git-restore-mtime - Restore original modification time of files based
7       on the date of the most recent commit that modified them
8

SYNOPSIS

10       git-restore-mtime [-h] [--quiet] [--verbose] [--force] [--merge]
11                         [--first-parent]
12                         [--skip-missing] [--no-directories] [--test]
13                         [--commit-time]
14                         [--work-tree WORKDIR] [--git-dir GITDIR]
15                         [pathspec [pathspec...]]
16

DESCRIPTION

18       Restore original modification time of files based on the date of the
19       most recent commit that modified them. Useful when generating release
20       tarballs.
21

OPTIONS

23   Positional arguments:
24       pathspec
25               only modify paths (dirs or files) matching PATHSPEC, relative
26               to current directory. Default is to modify all non-ignored,
27               tracked files.
28
29   Optional arguments:
30       -h, --help
31               show help message and exit
32
33       --quiet,-q
34               suppress informative messages and summary statistics.
35
36       --verbose,-v
37               print additional information for each processed file.
38               Overwrites --quiet.
39
40       --force,-f
41               force execution on trees with uncommitted changes.
42
43       --merge,-m
44               include merge commits. Leads to more recent mtimes and more
45               files per commit, thus with the same mtime (which may or may
46               not be what you want). Including merge commits may lead to less
47               commits being evaluated (all files are found sooner), which
48               improves performance, sometimes substantially. But since merge
49               commits are usually huge, processing them may also take longer,
50               sometimes substantially. By default merge logs are only used
51               for files missing from regular commit logs.
52
53       --first-parent
54               pass --first-parent to git whatchanged to hide the second
55               parent from the merge commit logs. Only has any effect if
56               --merge is also specified or --skip-missing is not specified
57               and there were files not found in regular commit logs.
58
59       --skip-missing,-s
60               do not try to find missing files. If some files were not found
61               in regular commit logs, by default it retries using merge
62               commit logs for these files (if --merge was not used already).
63               This option disables this behavior, which may slightly improve
64               performance, but files found only in merge commits will not be
65               updated.
66
67       --no-directories,-D
68               do not update directory mtime for files created, renamed or
69               deleted in it. Note: just modifying a file will not update its
70               directory mtime.
71
72       --test,-t
73               test run: do not actually update any file
74
75       --commit-time,-c
76               use commit time instead of author time
77
78       --work-tree WORKDIR
79               specify where the work tree is. Default for most repositories
80               is current directory.
81
82       --git-dir GITDIR
83               specify where the git repository is. Default for most
84               repositories <work-tree>/.git
85

SEE ALSO

87       https://github.com/MestreLion/git-tools
88

AUTHOR

90       Rodrigo Silva (MestreLion) linux@rodrigosilva.com
91
92
93
94                                  2016-01-31              GIT-RESTORE-MTIME(1)