.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-ARCHIVE" "1" "09/15/2007" "Git 1.5.3.1.91.gd3392" "Git Manual"
+.TH "GIT\-ARCHIVE" "1" "10/23/2007" "Git 1.5.3.4.319.gdd817" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.sp
.nf
\fIgit\-archive\fR \-\-format=<fmt> [\-\-list] [\-\-prefix=<prefix>/] [<extra>]
- [\-\-remote=<repo>] <tree\-ish> [path\&...]
+ [\-\-remote=<repo> [\-\-exec=<git\-upload\-archive>]] <tree\-ish>
+ [path\&...]
.fi
.SH "DESCRIPTION"
Creates an archive of the specified format containing the tree structure for the named tree, and writes it out to the standard output. If <prefix> is specified it is prepended to the filenames in the archive.
\-\-remote=<repo>
Instead of making a tar archive from local repository, retrieve a tar archive from a remote repository.
.TP
+\-\-exec=<git\-upload\-archive>
+Used with \-\-remote to specify the path to the git\-upload\-archive executable on the remote side.
+.TP
<tree\-ish>
The tree or commit to produce an archive for.
.TP
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-CHERRY\-PICK" "1" "07/19/2007" "Git 1.5.3.rc2.19.gc4fba" "Git Manual"
+.TH "GIT\-CHERRY\-PICK" "1" "10/23/2007" "Git 1.5.3.4.319.gdd817" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
With this option, git\-cherry\-pick will let you edit the commit message prior committing.
.TP
\-x
-Cause the command to append which commit was cherry\-picked after the original commit message when making a commit. Do not use this option if you are cherry\-picking from your private branch because the information is useless to the recipient. If on the other hand you are cherry\-picking between two publicly visible branches (e.g. backporting a fix to a maintenance branch for an older release from a development branch), adding this information can be useful.
+When recording the commit, append to the original commit message a note that indicates which commit this change was cherry\-picked from. Append the note only for cherry picks without conflicts. Do not use this option if you are cherry\-picking from your private branch because the information is useless to the recipient. If on the other hand you are cherry\-picking between two publicly visible branches (e.g. backporting a fix to a maintenance branch for an older release from a development branch), adding this information can be useful.
.TP
\-r
It used to be that the command defaulted to do \-x described above, and \-r was to disable it. Now the default is not to do \-x so this option is a no\-op.
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-CONFIG" "1" "10/03/2007" "Git 1.5.3.4.203.gcc61a" "Git Manual"
+.TH "GIT\-CONFIG" "1" "10/23/2007" "Git 1.5.3.4.319.gdd817" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
This setting is automatically guessed by \fBgit\-clone\fR(1) or \fBgit\-init\fR(1) when the repository was created. By default a repository that ends in "/.git" is assumed to be not bare (bare = false), while all other repositories are assumed to be bare (bare = true).
.TP
core.worktree
-Set the path to the working tree. The value will not be used in combination with repositories found automatically in a .git directory (i.e. $GIT_DIR is not set). This can be overriden by the GIT_WORK_TREE environment variable and the \fI\-\-work\-tree\fR command line option.
+Set the path to the working tree. The value will not be used in combination with repositories found automatically in a .git directory (i.e. $GIT_DIR is not set). This can be overridden by the GIT_WORK_TREE environment variable and the \fI\-\-work\-tree\fR command line option.
.TP
core.logAllRefUpdates
Enable the reflog. Updates to a ref <ref> is logged to the file "$GIT_DIR/logs/<ref>", by appending the new and old SHA1, the date/time and the reason of the update, but only when the file exists. If this configuration variable is set to true, missing "$GIT_DIR/logs/<ref>" file is automatically created for branch heads.
Controls which merge resolution program is used by \fBgit\-mergetool\fR(1). Valid values are: "kdiff3", "tkdiff", "meld", "xxdiff", "emerge", "vimdiff", "gvimdiff", and "opendiff".
.TP
merge.verbosity
-Controls the amount of output shown by the recursive merge strategy. Level 0 outputs nothing except a final error message if conflicts were detected. Level 1 outputs only conflicts, 2 outputs conflicts and file changes. Level 5 and above outputs debugging information. The default is level 2. Can be overriden by \fIGIT_MERGE_VERBOSITY\fR environment variable.
+Controls the amount of output shown by the recursive merge strategy. Level 0 outputs nothing except a final error message if conflicts were detected. Level 1 outputs only conflicts, 2 outputs conflicts and file changes. Level 5 and above outputs debugging information. The default is level 2. Can be overridden by \fIGIT_MERGE_VERBOSITY\fR environment variable.
.TP
merge.<driver>.name
Defines a human readable name for a custom low\-level merge driver. See \fBgitattributes\fR(5) for details.
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-DIFF" "1" "10/03/2007" "Git 1.5.3.4.203.gcc61a" "Git Manual"
+.TH "GIT\-DIFF" "1" "10/23/2007" "Git 1.5.3.4.319.gdd817" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.br
\fB2. \fRSame as above.
.br
-\fB3. \fRChanges that occured on the master branch since when the topic branch was started off it.
+\fB3. \fRChanges that occurred on the master branch since when the topic branch was started off it.
.br
.TP
Limiting the diff output
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-FILTER\-BRANCH" "1" "09/14/2007" "Git 1.5.3.1.56.g611d" "Git Manual"
+.TH "GIT\-FILTER\-BRANCH" "1" "10/23/2007" "Git 1.5.3.4.319.gdd817" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ft
.fi
-Now, you will get the rewritten history saved in the branch \fInewbranch\fR (your current branch is left untouched).
+Now, you will get the rewritten history saved in HEAD.
To set a commit (which typically is at the tip of another history) to be the parent of the current initial commit, in order to paste the other history behind the current history:
.sp
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-GC" "1" "10/03/2007" "Git 1.5.3.4.203.gcc61a" "Git Manual"
+.TH "GIT\-GC" "1" "10/23/2007" "Git 1.5.3.4.319.gdd817" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.SH "DESCRIPTION"
Runs a number of housekeeping tasks within the current repository, such as compressing file revisions (to reduce disk space and increase performance) and removing unreachable objects which may have been created from prior invocations of \fBgit\-add\fR(1).
-Users are encouraged to run this task on a regular basis within each repository to maintain good disk space utilization and good operating performance.
+Users are encouraged to run this task on a regular basis within each repository to maintain good disk space utilization and good operating performance. Some git commands may automatically run git\-gc; see the \-\-auto flag below for details.
.SH "OPTIONS"
.TP
\-\-prune
Usually \fIgit\-gc\fR runs very quickly while providing good disk space utilization and performance. This option will cause git\-gc to more aggressively optimize the repository at the expense of taking much more time. The effects of this optimization are persistent, so this option only needs to be used occasionally; every few hundred changesets or so.
.TP
\-\-auto
-With this option, git gc checks if there are too many loose objects in the repository and runs \fBgit\-repack\fR(1) with \-d \-l option to pack them. The threshold for loose objects is set with gc.auto configuration variable, and can be disabled by setting it to 0. Some Porcelain commands use this after they perform operation that could create many loose objects automatically. Additionally, when there are too many packs are present, they are consolidated into one larger pack by running the git\-repack command with \-A option. The threshold for number of packs is set with gc.autopacklimit configuration variable.
+With this option, git gc checks whether any housekeeping is required; if not, it exits without performing any work. Some git commands run git gc \-\-auto after performing operations that could create many loose objects.
+
+Housekeeping is required if there are too many loose objects or too many packs in the repository. If the number of loose objects exceeds the value of the gc.auto configuration variable, then all loose objects are combined into a single pack using git\-repack \-d \-l. Setting the value of gc.auto to 0 disables automatic packing of loose objects.
+
+If the number of packs exceeds the value of gc.autopacklimit, then existing packs (except those marked with a .keep file) are consolidated into a single pack by using the \-A option of git\-repack. Setting gc.autopacklimit to 0 disables automatic consolidation of packs.
.SH "CONFIGURATION"
The optional configuration variable \fIgc.reflogExpire\fR can be set to indicate how long historical entries within each branch's reflog should remain available in this repository. The setting is expressed as a length of time, for example \fI90 days\fR or \fI3 months\fR. It defaults to \fI90 days\fR.
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-INDEX\-PACK" "1" "07/19/2007" "Git 1.5.3.rc2.19.gc4fba" "Git Manual"
+.TH "GIT\-INDEX\-PACK" "1" "10/23/2007" "Git 1.5.3.4.319.gdd817" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
Write the generated pack index into the specified file. Without this option the name of pack index file is constructed from the name of packed archive file by replacing .pack with .idx (and the program fails if the name of packed archive does not end with .pack).
.TP
\-\-stdin
-When this flag is provided, the pack is read from stdin instead and a copy is then written to <pack\-file>. If <pack\-file> is not specified, the pack is written to objects/pack/ directory of the current git repository with a default name determined from the pack content. If <pack\-file> is not specified consider using \-\-keep to prevent a race condition between this process and \fB:git\-repack\fR(1) .
+When this flag is provided, the pack is read from stdin instead and a copy is then written to <pack\-file>. If <pack\-file> is not specified, the pack is written to objects/pack/ directory of the current git repository with a default name determined from the pack content. If <pack\-file> is not specified consider using \-\-keep to prevent a race condition between this process and \fB:git\-repack\fR(1).
.TP
\-\-fix\-thin
It is possible for \fBgit\-pack\-objects\fR(1) to build "thin" pack, which records objects in deltified form based on objects not included in the pack to reduce network traffic. Those objects are expected to be present on the receiving end and they must be included in the pack for that pack to be self contained and indexable. Without this option any attempt to index a thin pack will fail. This option only makes sense in conjunction with \-\-stdin.
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-INSTAWEB" "1" "07/19/2007" "Git 1.5.3.rc2.19.gc4fba" "Git Manual"
+.TH "GIT\-INSTAWEB" "1" "10/23/2007" "Git 1.5.3.4.319.gdd817" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
Only bind the web server to the local IP (127.0.0.1).
.TP
\-d|\-\-httpd
-The HTTP daemon command\-line that will be executed. Command\-line options may be specified here, and the configuration file will be added at the end of the command\-line. Currently, lighttpd and apache2 are the only supported servers. (Default: lighttpd)
+The HTTP daemon command\-line that will be executed. Command\-line options may be specified here, and the configuration file will be added at the end of the command\-line. Currently lighttpd, apache2 and webrick are supported. (Default: lighttpd)
.TP
\-m|\-\-module\-path
The module path (only needed if httpd is Apache). (Default: /usr/lib/apache2/modules)
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-MERGE\-INDEX" "1" "07/19/2007" "Git 1.5.3.rc2.19.gc4fba" "Git Manual"
+.TH "GIT\-MERGE\-INDEX" "1" "10/23/2007" "Git 1.5.3.4.319.gdd817" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
If "git\-merge\-index" is called with multiple <file>s (or \-a) then it processes them in turn only stopping if merge returns a non\-zero exit code.
-Typically this is run with the a script calling git's imitation of the merge command from the RCS package.
+Typically this is run with a script calling git's imitation of the merge command from the RCS package.
A sample script called "git\-merge\-one\-file" is included in the distribution.
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-PUSH" "1" "09/19/2007" "Git 1.5.3.1.153.g89df5" "Git Manual"
+.TH "GIT\-PUSH" "1" "10/23/2007" "Git 1.5.3.4.319.gdd817" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.SH "SYNOPSIS"
.sp
.nf
-\fIgit\-push\fR [\-\-all] [\-\-tags] [\-\-receive\-pack=<git\-receive\-pack>]
+\fIgit\-push\fR [\-\-all] [\-\-dry\-run] [\-\-tags] [\-\-receive\-pack=<git\-receive\-pack>]
[\-\-repo=all] [\-f | \-\-force] [\-v] [<repository> <refspec>\&...]
.fi
.SH "DESCRIPTION"
\-\-all
Instead of naming each ref to push, specifies that all refs under $GIT_DIR/refs/heads/ be pushed.
.TP
+\-\-dry\-run
+Do everything except actually send the updates.
+.TP
\-\-tags
All refs under $GIT_DIR/refs/tags are pushed, in addition to refspecs explicitly listed on the command line.
.TP
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-REBASE" "1" "09/30/2007" "Git 1.5.3.3.126.g72dc" "Git Manual"
+.TH "GIT\-REBASE" "1" "10/23/2007" "Git 1.5.3.4.319.gdd817" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
The current branch is reset to <upstream>, or <newbase> if the \-\-onto option was supplied. This has the exact same effect as git reset \-\-hard <upstream> (or <newbase>).
-The commits that were previously saved into the temporary area are then reapplied to the current branch, one by one, in order.
+The commits that were previously saved into the temporary area are then reapplied to the current branch, one by one, in order. Note that any commits in HEAD which introduce the same textual changes as a commit in HEAD..<upstream> are omitted (i.e., a patch already accepted upstream with a different commit message or timestamp will be skipped).
It is possible that a merge failure will prevent this process from being completely automatic. You will have to resolve any such merge failure and run git rebase \-\-continue. Another option is to bypass the commit that caused the merge failure with git rebase \-\-skip. To restore the original <branch> and remove the .dotest working files, use the command git rebase \-\-abort instead.
.fi
The latter form is just a short\-hand of git checkout topic followed by git rebase master.
+If the upstream branch already contains a change you have made (e.g., because you mailed a patch which was applied upstream), then that commit will be skipped. For example, running git\-rebase master on the following history (in which A' and A introduce the same set of changes, but have different committer information):
+.sp
+.nf
+.ft C
+ A\-\-\-B\-\-\-C topic
+ /
+ D\-\-\-E\-\-\-A'\-\-\-F master
+.ft
+
+.fi
+will result in:
+.sp
+.nf
+.ft C
+ B'\-\-\-C' topic
+ /
+ D\-\-\-E\-\-\-A'\-\-\-F master
+.ft
+
+.fi
Here is how you would transplant a topic branch based on one branch to another, to pretend that you forked the topic branch from the latter branch, using rebase \-\-onto.
First let's assume your \fItopic\fR is based on branch \fInext\fR. For example feature developed in \fItopic\fR depends on some functionality which is found in \fInext\fR.
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-REFLOG" "1" "08/25/2007" "Git 1.5.3.rc6.23.g0058" "Git Manual"
+.TH "GIT\-REFLOG" "1" "10/23/2007" "Git 1.5.3.4.319.gdd817" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
The command takes various subcommands, and different options depending on the subcommand:
.sp
.nf
-git reflog expire [\-\-dry\-run] [\-\-stale\-fix]
+git reflog expire [\-\-dry\-run] [\-\-stale\-fix] [\-\-verbose]
[\-\-expire=<time>] [\-\-expire\-unreachable=<time>] [\-\-all] <refs>\&...
.fi
git reflog [show] [log\-options]
.TP
\-\-all
Instead of listing <refs> explicitly, prune all refs.
+.TP
+\-\-verbose
+Print extra information on screen.
.SH "AUTHOR"
Written by Junio C Hamano <junkio@cox.net>
.SH "DOCUMENTATION"
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-SEND\-PACK" "1" "09/19/2007" "Git 1.5.3.1.153.g89df5" "Git Manual"
+.TH "GIT\-SEND\-PACK" "1" "10/23/2007" "Git 1.5.3.4.319.gdd817" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.SH "NAME"
git\-send\-pack \- Push objects over git protocol to another repository
.SH "SYNOPSIS"
-\fIgit\-send\-pack\fR [\-\-all] [\-\-force] [\-\-receive\-pack=<git\-receive\-pack>] [\-\-verbose] [\-\-thin] [<host>:]<directory> [<ref>\&...]
+\fIgit\-send\-pack\fR [\-\-all] [\-\-dry\-run] [\-\-force] [\-\-receive\-pack=<git\-receive\-pack>] [\-\-verbose] [\-\-thin] [<host>:]<directory> [<ref>\&...]
.SH "DESCRIPTION"
Usually you would want to use \fBgit\-push\fR(1) which is a higher level wrapper of this command instead.
\-\-all
Instead of explicitly specifying which refs to update, update all heads that locally exist.
.TP
+\-\-dry\-run
+Do everything except actually send the updates.
+.TP
\-\-force
Usually, the command refuses to update a remote ref that is not an ancestor of the local ref used to overwrite it. This flag disables the check. What this means is that the remote repository can lose commits; use it with care.
.TP
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-STASH" "1" "10/01/2007" "Git 1.5.3.3.131.g34c6d" "Git Manual"
+.TH "GIT\-STASH" "1" "10/23/2007" "Git 1.5.3.4.319.gdd817" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.fi
.TP
show [<stash>]
-Show the changes recorded in the stash as a diff between the the stashed state and its original parent. When no <stash> is given, shows the latest one. By default, the command shows the diffstat, but it will accept any format known to git\-diff (e.g., git\-stash show \-p stash@{1} to view the second most recent stash in patch form).
+Show the changes recorded in the stash as a diff between the stashed state and its original parent. When no <stash> is given, shows the latest one. By default, the command shows the diffstat, but it will accept any format known to git\-diff (e.g., git\-stash show \-p stash@{1} to view the second most recent stash in patch form).
.TP
apply [\-\-index] [<stash>]
Restore the changes recorded in the stash on top of the current working tree state. When no <stash> is given, applies the latest one. The working directory must match the index.
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-SVN" "1" "09/19/2007" "Git 1.5.3.1.153.g89df5" "Git Manual"
+.TH "GIT\-SVN" "1" "10/23/2007" "Git 1.5.3.4.319.gdd817" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
Additionally, only one of these four options can be used per\-svn\-remote section because they affect the \fIgit\-svn\-id:\fR metadata line.
.SH "BASIC EXAMPLES"
-Tracking and contributing to a the trunk of a Subversion\-managed project:
+Tracking and contributing to the trunk of a Subversion\-managed project:
.sp
.nf
.ft C
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-TAG" "1" "08/28/2007" "Git 1.5.3.rc6.54.g9277" "Git Manual"
+.TH "GIT\-TAG" "1" "10/23/2007" "Git 1.5.3.4.319.gdd817" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
2.
The insane thing. You really want to call the new version "X" too, \fIeven though\fR others have already seen the old one. So just use "git tag \-f" again, as if you hadn't already published the old one.
-However, Git does \fBnot\fR (and it should not)change tags behind users back. So if somebody already got the old tag, doing a "git pull" on your tree shouldn't just make them overwrite the old one.
+However, Git does \fBnot\fR (and it should not) change tags behind users back. So if somebody already got the old tag, doing a "git pull" on your tree shouldn't just make them overwrite the old one.
If somebody got a release tag from you, you cannot just change the tag for them by updating your own one. This is a big security issue, in that people MUST be able to trust their tag\-names. If you really want to do the insane thing, you need to just fess up to it, and tell people that you messed up. You can do that by making a very public announcement saying:
.sp
A one\-shot pull is a sign that a commit history is now crossing the boundary between one circle of people (e.g. "people who are primarily interested in networking part of the kernel") who may have their own set of tags (e.g. "this is the third release candidate from the networking group to be proposed for general consumption with 2.6.21 release") to another circle of people (e.g. "people who integrate various subsystem improvements"). The latter are usually not interested in the detailed tags used internally in the former group (that is what "internal" means). That is why it is desirable not to follow tags automatically in this case.
It may well be that among networking people, they may want to exchange the tags internal to their group, but in that workflow they are most likely tracking with each other's progress by having tracking branches. Again, the heuristic to automatically follow such tags is a good thing.
+.SS "On Backdating Tags"
+If you have imported some changes from another VCS and would like to add tags for major releases of your work, it is useful to be able to specify the date to embed inside of the tag object. The data in the tag object affects, for example, the ordering of tags in the gitweb interface.
+
+To set the date used in future tag objects, set the environment variable GIT_AUTHOR_DATE to one or more of the date and time. The date and time can be specified in a number of ways; the most common is "YYYY\-MM\-DD HH:MM".
+
+An example follows.
+.sp
+.nf
+.ft C
+$ GIT_AUTHOR_DATE="2006\-10\-02 10:31" git tag \-s v1.0.1
+.ft
+
+.fi
.SH "AUTHOR"
Written by Linus Torvalds <torvalds@osdl.org>, Junio C Hamano <junkio@cox.net> and Chris Wright <chrisw@osdl.org>.
.SH "DOCUMENTATION"
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GITK" "1" "07/19/2007" "Git 1.5.3.rc2.19.gc4fba" "Git Manual"
+.TH "GITK" "1" "10/23/2007" "Git 1.5.3.4.319.gdd817" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
gitk \-\-since="2 weeks ago" \-\- gitk
Show the changes during the last two weeks to the file \fIgitk\fR. The "\-\-" is necessary to avoid confusion with the \fBbranch\fR named \fIgitk\fR
.TP
-gitk \-\-max\-count=100 \-\-all \(em Makefile
+gitk \-\-max\-count=100 \-\-all \-\- Makefile
Show at most 100 changes made to the file \fIMakefile\fR. Instead of only looking for changes in the current branch look in all branches.
.SH "SEE ALSO"
.TP
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT" "7" "10/04/2007" "Git 1.5.3.4.206.g58ba4" "Git Manual"
+.TH "GIT" "7" "10/23/2007" "Git 1.5.3.4.319.gdd817" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
For a more complete list of ways to spell object names, see "SPECIFYING REVISIONS" section in \fBgit\-rev\-parse\fR(1).
.SH "FILE/DIRECTORY STRUCTURE"
-Please see [8]\&\fIrepository layout\fR document.
+Please see the [8]\&\fIrepository layout\fR document.
Read [9]\&\fIhooks\fR for more details about each hook.
Higher level SCMs may provide and manage additional information in the $GIT_DIR.
.SH "TERMINOLOGY"
-Please see [10]\&\fIglossary\fR document.
+Please see the [10]\&\fIglossary\fR document.
.SH "ENVIRONMENT VARIABLES"
Various git commands use the following environment variables:
.SS "The git Repository"
projects / git.git / commitdiff