2 .\" Copyright (c) 2017 Martin Pieuchot
3 .\" Copyright (c) 2018, 2019, 2020 Stefan Sperling
5 .\" Permission to use, copy, modify, and distribute this software for any
6 .\" purpose with or without fee is hereby granted, provided that the above
7 .\" copyright notice and this permission notice appear in all copies.
9 .\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
10 .\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
11 .\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
12 .\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
13 .\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
14 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
15 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
30 is a version control system which stores the history of tracked files
31 in a Git repository, as used by the Git version control system.
32 This repository format is described in
33 .Xr git-repository 5 .
38 version control system because every copy of a repository is writeable.
39 Modifications made to files can be synchronized between repositories
44 must be checked out from the repository for modification.
45 Checked out files are stored in a
47 which can be placed at an arbitrary directory in the filesystem hierarchy.
48 The on-disk format of this work tree is described in
52 provides global and command-specific options.
53 Global options must precede the command name, and are as follows:
54 .Bl -tag -width tenletters
56 Display usage information and exit immediately.
58 Display program version and exit immediately.
64 .Bl -tag -width checkout
65 .It Cm init Ar repository-path
66 Create a new empty repository at the specified
73 command must be used to populate the empty repository before
76 .It Cm import Oo Fl b Ar branch Oc Oo Fl m Ar message Oc Oo Fl r Ar repository-path Oc Oo Fl I Ar pattern Oc Ar directory
77 Create an initial commit in a repository from the file hierarchy
80 The created commit will not have any parent commits, i.e. it will be a
82 Also create a new reference which provides a branch name for the newly
84 Show the path of each imported file to indicate progress.
90 environment variable to be set,
91 unless an author has been configured in
97 configuration settings can be obtained from the repository's
99 file or from Git's global
110 instead of creating the default branch
112 Use of this option is required if the
114 branch already exists.
116 Use the specified log message when creating the new commit.
121 opens a temporary file in an editor where a log message can be written.
122 .It Fl r Ar repository-path
123 Use the repository at the specified path.
124 If not specified, assume the repository is located at or above the current
127 Ignore files or directories with a name which matches the specified
129 This option may be specified multiple times to build a list of ignore patterns.
132 follows the globbing rules documented in
138 .It Cm clone Oo Fl a Oc Oo Fl b Ar branch Oc Oo Fl l Oc Oo Fl m Oc Oo Fl q Oc Oo Fl v Oc Oo Fl R Ar reference Oc Ar repository-URL Op Ar directory
139 Clone a Git repository at the specified
145 is specified the directory name will be derived from the name of the
148 will refuse to run if the
154 specifies a protocol scheme, a server hostname, an optional port number
155 separated from the hostname by a colon, and a path to the repository on
157 .Lk scheme://hostname:port/path/to/repository
159 The following protocol schemes are supported:
160 .Bl -tag -width git+ssh
162 The Git protocol as implemented by the
165 Use of this protocol is discouraged since it supports neither authentication
168 The Git protocol wrapped in an authenticated and encrypted
171 With this protocol the hostname may contain an embedded username for
176 Short alias for git+ssh.
179 Objects in the cloned repository are stored in a pack file which is downloaded
181 This pack file will then be indexed to facilitate access to the objects stored
183 If any objects in the pack file are stored in deltified form, all deltas will
184 be fully resolved in order to compute the ID of such objects.
185 This can take some time.
186 More details about the pack file format are documented in
187 .Xr git-repository 5 .
190 creates a remote repository entry in the
194 files of the cloned repository to store the
200 arguments for future use by
210 Fetch all branches from the remote repository's
212 reference namespace and set
213 .Cm fetch-all-branches
214 in the cloned repository's
216 file for future use by
218 If this option is not specified, a branch resolved via the remote
219 repository's HEAD reference will be fetched.
220 Cannot be used together with the
226 from the remote repository's
229 This option may be specified multiple times to build a list of branches
231 If the branch corresponding to the remote repository's HEAD reference is not
232 in this list, the cloned repository's HEAD reference will be set to the first
233 branch which was fetched.
234 If this option is not specified, a branch resolved via the remote
235 repository's HEAD reference will be fetched.
236 Cannot be used together with the
240 List branches and tags available for fetching from the remote repository
241 and exit immediately.
242 Cannot be used together with any of the other options except
247 Create the cloned repository as a mirror of the original repository.
248 This is useful if the cloned repository will not be used to store
249 locally created commits.
255 files will be set up with the
257 option enabled, such that
261 will write incoming changes directly to branches in the
263 reference namespace, rather than to branches in the
266 This avoids the usual requirement of having to run
270 in order to make incoming changes appear on branches in the
273 But maintaining custom changes in the cloned repository becomes difficult
274 since such changes will be at risk of being discarded whenever incoming
277 Suppress progress reporting output.
278 The same option will be passed to
285 to print debugging messages to standard error output.
286 This option will be passed to
289 Multiple -v options increase the verbosity.
291 .It Fl R Ar reference
292 In addition to the branches and tags that will be fetched, fetch an arbitrary
294 from the remote repository's
297 This option may be specified multiple times to build a list of additional
301 may either be a path to a specific reference, or a reference namespace
302 which will cause all references in this namespace to be fetched.
304 Each reference will be mapped into the cloned repository's
306 namespace, unless the
308 option is used to mirror references directly into the cloned repository's
313 will refuse to fetch references from the remote repository's
322 .It Cm fetch Oo Fl a Oc Oo Fl b Ar branch Oc Oo Fl d Oc Oo Fl l Oc Oo Fl r Ar repository-path Oc Oo Fl t Oc Oo Fl q Oc Oo Fl v Oc Oo Fl R Ar reference Oc Op Ar remote-repository
323 Fetch new changes from a remote repository.
325 .Ar remote-repository
329 The remote repository's URL is obtained from the corresponding entry in
333 file of the local repository, as created by
336 New changes will be stored in a separate pack file downloaded from the server.
337 Optionally, separate pack files stored in the repository can be combined with
340 By default, branch references in the
342 reference namespace will be updated to point at the newly fetched commits.
345 command can then be used to make new changes visible on branches in the
347 namespace, merging incoming changes with the changes on those branches
350 If the repository was created as a mirror with
352 then all branches in the
354 namespace will be updated directly to match the corresponding branches in
355 the remote repository.
356 If those branches contained local commits, these commits will no longer be
357 reachable via a reference and will therefore be at risk of being discarded
358 by Git's garbage collector or
359 .Cm gotadmin cleanup .
360 Maintaining custom changes in a mirror repository is therefore discouraged.
362 In any case, references in the
364 namespace will always be fetched and mapped directly to local references
365 in the same namespace.
372 Fetch all branches from the remote repository's
375 This option can be enabled by default for specific repositories in
377 If this option is not specified, a branch resolved via the remote
378 repository's HEAD reference will be fetched.
379 Cannot be used together with the
385 from the remote repository's
388 This option may be specified multiple times to build a list of branches
390 If this option is not specified, a branch resolved via the remote
391 repository's HEAD reference will be fetched.
392 Cannot be used together with the
396 Delete branches and tags from the local repository which are no longer
397 present in the remote repository.
398 Only references are deleted.
399 Any commit, tree, tag, and blob objects belonging to deleted branches or
400 tags remain in the repository and may be removed separately with
401 Git's garbage collector or
402 .Cm gotadmin cleanup .
404 List branches and tags available for fetching from the remote repository
405 and exit immediately.
406 Cannot be used together with any of the other options except
412 Allow existing references in the
414 namespace to be updated if they have changed on the server.
415 If not specified, only new tag references will be created.
416 .It Fl r Ar repository-path
417 Use the repository at the specified path.
418 If not specified, assume the repository is located at or above the current
420 If this directory is a
422 work tree, use the repository path associated with this work tree.
424 Suppress progress reporting output.
425 The same option will be passed to
432 to print debugging messages to standard error output.
433 The same option will be passed to
436 Multiple -v options increase the verbosity.
438 .It Fl R Ar reference
439 In addition to the branches and tags that will be fetched, fetch an arbitrary
441 from the remote repository's
444 This option may be specified multiple times to build a list of additional
448 may either be a path to a specific reference, or a reference namespace
449 which will cause all references in this namespace to be fetched.
451 Each reference will be mapped into the local repository's
453 namespace, unless the local repository was created as a mirror with
455 in which case references will be mapped directly into the local repository's
459 Once a reference has been fetched, a branch based on it can be created with
464 will refuse to fetch references from the remote repository's
473 .It Cm checkout Oo Fl E Oc Oo Fl b Ar branch Oc Oo Fl c Ar commit Oc Oo Fl p Ar path-prefix Oc Ar repository-path Op Ar work-tree-path
474 Copy files from a repository into a new work tree.
475 Show the status of each affected file, using the following status codes:
476 .Bl -column YXZ description
477 .It A Ta new file was added
478 .It E Ta file already exists in work tree's meta-data
483 is not specified, either use the last component of
484 .Ar repository path ,
487 was specified use the last component of
495 Proceed with the checkout operation even if the directory at
498 Existing files will be left intact.
500 Check out files from a commit on the specified
502 If this option is not specified, a branch resolved via the repository's HEAD
503 reference will be used.
505 Check out files from the specified
507 on the selected branch.
508 The expected argument is a commit ID SHA1 hash or an existing reference
509 or tag name which will be resolved to a commit ID.
510 An abbreviated hash argument will be expanded to a full SHA1 hash
511 automatically, provided the abbreviation is unique.
512 If this option is not specified, the most recent commit on the selected
517 is not contained in the selected branch, a different branch which contains
518 this commit must be specified with the
521 If no such branch is known a new branch must be created for this
527 Checking out work trees with an unknown branch is intentionally not supported.
528 .It Fl p Ar path-prefix
529 Restrict the work tree to a subset of the repository's tree hierarchy.
530 Only files beneath the specified
537 .It Cm update Oo Fl b Ar branch Oc Oo Fl c Ar commit Oc Op Ar path ...
538 Update an existing work tree to a different
540 Change existing files in the work tree as necessary to match file contents
542 Preserve any local changes in the work tree and merge them with the
545 Files which already contain merge conflicts will not be updated to avoid
546 further complications.
547 Such files will be updated when
549 is run again after merge conflicts have been resolved.
550 If the conflicting changes are no longer needed affected files can be
557 Show the status of each affected file, using the following status codes:
558 .Bl -column YXZ description
559 .It U Ta file was updated and contained no local changes
560 .It G Ta file was updated and local changes were merged cleanly
561 .It C Ta file was updated and conflicts occurred during merge
562 .It D Ta file was deleted
563 .It A Ta new file was added
564 .It \(a~ Ta versioned file is obstructed by a non-regular file
565 .It ! Ta a missing versioned file was restored
566 .It # Ta file was not updated because it contains merge conflicts
567 .It ? Ta changes destined for an unversioned file were not merged
572 is specified, update the entire work tree.
573 Otherwise, restrict the update operation to files at or within the
575 Each path is required to exist in the update operation's target commit.
576 Files in the work tree outside specified paths will remain unchanged and
577 will retain their previously recorded base commit.
580 commands may refuse to run while the work tree contains files from
581 multiple base commits.
582 The base commit of such a work tree can be made consistent by running
584 across the entire work tree.
587 is incompatible with the
592 cannot update paths with staged changes.
593 If changes have been staged with
595 these changes must first be committed with
605 Switch the work tree's branch reference to the specified
607 before updating the work tree.
608 This option requires that all paths in the work tree are updated.
610 As usual, any local changes in the work tree will be preserved.
611 This can be useful when switching to a newly created branch in order
612 to commit existing local changes to this branch.
614 Any local changes must be dealt with separately in order to obtain a
615 work tree with pristine file contents corresponding exactly to the specified
617 Such changes could first be committed to a different branch with
619 or could be discarded with
622 Update the work tree to the specified
624 The expected argument is a commit ID SHA1 hash or an existing reference
625 or tag name which will be resolved to a commit ID.
626 An abbreviated hash argument will be expanded to a full SHA1 hash
627 automatically, provided the abbreviation is unique.
628 If this option is not specified, the most recent commit on the work tree's
634 .It Cm status Oo Fl I Oc Oo Fl s Ar status-codes Oc Op Ar path ...
635 Show the current modification status of files in a work tree,
636 using the following status codes:
637 .Bl -column YXZ description
638 .It M Ta modified file
639 .It A Ta file scheduled for addition in next commit
640 .It D Ta file scheduled for deletion in next commit
641 .It C Ta modified or added file which contains merge conflicts
642 .It ! Ta versioned file was expected on disk but is missing
643 .It \(a~ Ta versioned file is obstructed by a non-regular file
644 .It ? Ta unversioned item not tracked by
646 .It m Ta modified file modes (executable bit only)
647 .It N Ta non-existent
649 specified on the command line
654 is specified, show modifications in the entire work tree.
655 Otherwise, show modifications at or within the specified paths.
657 If changes have been staged with
659 staged changes are shown in the second output column, using the following
661 .Bl -column YXZ description
662 .It M Ta file modification is staged
663 .It A Ta file addition is staged
664 .It D Ta file deletion is staged
667 Changes created on top of staged changes are indicated in the first column:
668 .Bl -column YXZ description
669 .It MM Ta file was modified after earlier changes have been staged
670 .It MA Ta file was modified after having been staged for addition
678 Show unversioned files even if they match an ignore pattern.
679 .It Fl s Ar status-codes
680 Only show files with a modification status matching any of the
681 single-character status codes contained in the
684 Any combination of codes from the above list of possible status codes
686 For staged files, status codes displayed in either column will be matched.
689 For compatibility with
700 files in each traversed directory and will not display unversioned files
701 which match these patterns.
706 supports consecutive asterisks,
708 which will match an arbitrary amount of directories.
712 only supports a single ignore pattern per line.
716 does not support negated ignore patterns prefixed with
718 and gives no special significance to the location of path component separators,
724 .It Cm log Oo Fl b Oc Oo Fl c Ar commit Oc Oo Fl C Ar number Oc Oo Fl l Ar N Oc Oo Fl p Oc Oo Fl P Oc Oo Fl s Ar search-pattern Oc Oo Fl r Ar repository-path Oc Oo Fl R Oc Oo Fl x Ar commit Oc Op Ar path
725 Display history of a repository.
728 is specified, show only commits which modified this path.
729 If invoked in a work tree, the
731 is interpreted relative to the current working directory,
732 and the work tree's path prefix is implicitly prepended.
733 Otherwise, the path is interpreted relative to the repository root.
740 Display individual commits which were merged into the current branch
744 shows the linear history of the current branch only.
746 Start traversing history at the specified
748 The expected argument is a commit ID SHA1 hash or an existing reference
749 or tag name which will be resolved to a commit ID.
750 An abbreviated hash argument will be expanded to a full SHA1 hash
751 automatically, provided the abbreviation is unique.
752 If this option is not specified, default to the work tree's current branch
753 if invoked in a work tree, or to the repository's HEAD reference.
755 Set the number of context lines shown in diffs with
757 By default, 3 lines of context are shown.
759 Limit history traversal to a given number of commits.
760 If this option is not specified, a default limit value of zero is used,
761 which is treated as an unbounded limit.
763 .Ev GOT_LOG_DEFAULT_LIMIT
764 environment variable may be set to change this default value.
766 Display the patch of modifications made in each commit.
769 is specified, only show the patch of modifications at or within this path.
771 Display the list of file paths changed in each commit, using the following
773 .Bl -column YXZ description
774 .It M Ta modified file
775 .It D Ta file was deleted
776 .It A Ta new file was added
777 .It m Ta modified file modes (executable bit only)
779 .It Fl s Ar search-pattern
780 If specified, show only commits with a log message matched by the extended
783 When used together with
785 then the file paths changed by a commit can be matched as well.
786 Regular expression syntax is documented in
788 .It Fl r Ar repository-path
789 Use the repository at the specified path.
790 If not specified, assume the repository is located at or above the current
792 If this directory is a
794 work tree, use the repository path associated with this work tree.
796 Determine a set of commits to display as usual, but display these commits
799 Stop traversing commit history immediately after the specified
802 This option has no effect if the specified
806 .It Cm diff Oo Fl a Oc Oo Fl C Ar number Oc Oo Fl r Ar repository-path Oc Oo Fl s Oc Oo Fl w Oc Op Ar object1 Ar object2 | Ar path
807 When invoked within a work tree with less than two arguments, display
808 local changes in the work tree.
811 is specified, only show changes within this path.
813 If two arguments are provided, treat each argument as a reference, a tag
814 name, or an object ID SHA1 hash, and display differences between the
815 corresponding objects.
816 Both objects must be of the same type (blobs, trees, or commits).
817 An abbreviated hash argument will be expanded to a full SHA1 hash
818 automatically, provided the abbreviation is unique.
825 Treat file contents as ASCII text even if binary data is detected.
827 Set the number of context lines shown in the diff.
828 By default, 3 lines of context are shown.
829 .It Fl r Ar repository-path
830 Use the repository at the specified path.
831 If not specified, assume the repository is located at or above the current
833 If this directory is a
835 work tree, use the repository path associated with this work tree.
837 Show changes staged with
839 instead of showing local changes in the work tree.
840 This option is only valid when
842 is invoked in a work tree.
844 Ignore whitespace-only changes.
849 .It Cm blame Oo Fl c Ar commit Oc Oo Fl r Ar repository-path Oc Ar path
850 Display line-by-line history of a file at the specified path.
857 Start traversing history at the specified
859 The expected argument is a commit ID SHA1 hash or an existing reference
860 or tag name which will be resolved to a commit ID.
861 An abbreviated hash argument will be expanded to a full SHA1 hash
862 automatically, provided the abbreviation is unique.
863 .It Fl r Ar repository-path
864 Use the repository at the specified path.
865 If not specified, assume the repository is located at or above the current
867 If this directory is a
869 work tree, use the repository path associated with this work tree.
874 .It Cm tree Oo Fl c Ar commit Oc Oo Fl r Ar repository-path Oc Oo Fl i Oc Oo Fl R Oc Op Ar path
875 Display a listing of files and directories at the specified
876 directory path in the repository.
877 Entries shown in this listing may carry one of the following trailing
879 .Bl -column YXZ description
880 .It @ Ta entry is a symbolic link
881 .It / Ta entry is a directory
882 .It * Ta entry is an executable file
883 .It $ Ta entry is a Git submodule
886 Symbolic link entries are also annotated with the target path of the link.
890 is specified, list the repository path corresponding to the current
891 directory of the work tree, or the root directory of the repository
892 if there is no work tree.
899 List files and directories as they appear in the specified
901 The expected argument is a commit ID SHA1 hash or an existing reference
902 or tag name which will be resolved to a commit ID.
903 An abbreviated hash argument will be expanded to a full SHA1 hash
904 automatically, provided the abbreviation is unique.
905 .It Fl r Ar repository-path
906 Use the repository at the specified path.
907 If not specified, assume the repository is located at or above the current
909 If this directory is a
911 work tree, use the repository path associated with this work tree.
913 Show object IDs of files (blob objects) and directories (tree objects).
915 Recurse into sub-directories in the repository.
920 .It Cm ref Oo Fl r Ar repository-path Oc Oo Fl l Oc Oo Fl c Ar object Oc Oo Fl s Ar reference Oc Oo Fl d Oc Op Ar name
921 Manage references in a repository.
923 References may be listed, created, deleted, and changed.
924 When creating, deleting, or changing a reference the specified
926 must be an absolute reference name, i.e. it must begin with
933 .It Fl r Ar repository-path
934 Use the repository at the specified path.
935 If not specified, assume the repository is located at or above the current
937 If this directory is a
939 work tree, use the repository path associated with this work tree.
941 List references in the repository.
944 is specified, list all existing references in the repository.
947 is a reference namespace, list all references in this namespace.
948 Otherwise, show only the reference with the given
950 Cannot be used together with any other options except
953 Create a reference or change an existing reference.
954 The reference with the specified
956 will point at the specified
960 argument is a ID SHA1 hash or an existing reference or tag name which will
961 be resolved to the ID of a corresponding commit, tree, tag, or blob object.
962 Cannot be used together with any other options except
964 .It Fl s Ar reference
965 Create a symbolic reference, or change an existing symbolic reference.
966 The symbolic reference with the specified
968 will point at the specified
970 which must already exist in the repository.
971 Care should be taken not to create loops between references when
973 Cannot be used together with any other options except
976 Delete the reference with the specified
979 Any commit, tree, tag, and blob objects belonging to deleted references
980 remain in the repository and may be removed separately with
981 Git's garbage collector or
982 .Cm gotadmin cleanup .
983 Cannot be used together with any other options except
986 .It Cm branch Oo Fl c Ar commit Oc Oo Fl r Ar repository-path Oc Oo Fl l Oc Oo Fl d Ar name Oc Oo Fl n Oc Op Ar name
987 Create, list, or delete branches.
989 Local branches are managed via references which live in the
994 command creates or deletes references in this namespace only.
996 If invoked in a work tree without any arguments, print the name of the
997 work tree's current branch.
1001 argument is passed, attempt to create a branch reference with the given name.
1002 By default the new branch reference will point at the latest commit on the
1003 work tree's current branch if invoked in a work tree, and otherwise to a commit
1004 resolved via the repository's HEAD reference.
1006 If invoked in a work tree, once the branch was created successfully
1007 switch the work tree's head reference to the newly created branch and
1008 update files across the entire work tree, just like
1009 .Cm got update -b Ar name
1011 Show the status of each affected file, using the following status codes:
1012 .Bl -column YXZ description
1013 .It U Ta file was updated and contained no local changes
1014 .It G Ta file was updated and local changes were merged cleanly
1015 .It C Ta file was updated and conflicts occurred during merge
1016 .It D Ta file was deleted
1017 .It A Ta new file was added
1018 .It \(a~ Ta versioned file is obstructed by a non-regular file
1019 .It ! Ta a missing versioned file was restored
1027 Make a newly created branch reference point at the specified
1031 argument is a commit ID SHA1 hash or an existing reference
1032 or tag name which will be resolved to a commit ID.
1033 .It Fl r Ar repository-path
1034 Use the repository at the specified path.
1035 If not specified, assume the repository is located at or above the current
1037 If this directory is a
1039 work tree, use the repository path associated with this work tree.
1041 List all existing branches in the repository, including copies of remote
1042 repositories' branches in the
1044 reference namespace.
1046 If invoked in a work tree, the work tree's current branch is shown
1047 with one the following annotations:
1048 .Bl -column YXZ description
1049 .It * Ta work tree's base commit matches the branch tip
1050 .It \(a~ Ta work tree's base commit is out-of-date
1053 Delete the branch with the specified name from the repository.
1054 Only the branch reference is deleted.
1055 Any commit, tree, and blob objects belonging to the branch
1056 remain in the repository and may be removed separately with
1057 Git's garbage collector or
1058 .Cm gotadmin cleanup .
1060 Do not switch and update the work tree after creating a new branch.
1065 .It Cm tag Oo Fl c Ar commit Oc Oo Fl m Ar message Oc Oo Fl r Ar repository-path Oc Oo Fl l Oc Ar name
1066 Manage tags in a repository.
1068 Tags are managed via references which live in the
1070 reference namespace.
1073 command operates on references in this namespace only.
1074 References in this namespace point at tag objects which contain a pointer
1075 to another object, a tag message, as well as author and timestamp information.
1077 Attempt to create a tag with the given
1079 and make this tag point at the given
1081 If no commit is specified, default to the latest commit on the work tree's
1082 current branch if invoked in a work tree, and to a commit resolved via
1083 the repository's HEAD reference otherwise.
1090 Make the newly created tag reference point at the specified
1094 argument is a commit ID SHA1 hash or an existing reference or tag name which
1095 will be resolved to a commit ID.
1096 An abbreviated hash argument will be expanded to a full SHA1 hash
1097 automatically, provided the abbreviation is unique.
1099 Use the specified tag message when creating the new tag.
1104 opens a temporary file in an editor where a tag message can be written.
1105 .It Fl r Ar repository-path
1106 Use the repository at the specified path.
1107 If not specified, assume the repository is located at or above the current
1109 If this directory is a
1111 work tree, use the repository path associated with this work tree.
1113 List all existing tags in the repository instead of creating a new tag.
1114 If this option is used, no other command-line arguments are allowed.
1119 command will not delete tags or change existing tags.
1120 If a tag must be deleted, the
1122 command may be used to delete a tag's reference.
1123 This should only be done if the tag has not already been copied to
1125 .It Cm add Oo Fl R Oc Oo Fl I Oc Ar path ...
1126 Schedule unversioned files in a work tree for addition to the
1127 repository in the next commit.
1128 By default, files which match a
1130 ignore pattern will not be added.
1137 Permit recursion into directories.
1138 If this option is not specified,
1140 will refuse to run if a specified
1144 Add files even if they match a
1148 .It Cm remove Oo Fl f Oc Oo Fl k Oc Oo Fl R Oc Oo Fl s Ar status-codes Oc Ar path ...
1149 Remove versioned files from a work tree and schedule them for deletion
1150 from the repository in the next commit.
1157 Perform the operation even if a file contains local modifications.
1159 Keep affected files on disk.
1161 Permit recursion into directories.
1162 If this option is not specified,
1164 will refuse to run if a specified
1167 .It Fl s Ar status-codes
1168 Only delete files with a modification status matching one of the
1169 single-character status codes contained in the
1172 The following status codes may be specified:
1173 .Bl -column YXZ description
1174 .It M Ta modified file (this implies the
1177 .It ! Ta versioned file expected on disk but missing
1183 .It Cm revert Oo Fl p Oc Oo Fl F Ar response-script Oc Oo Fl R Oc Ar path ...
1184 Revert any local changes in files at the specified paths in a work tree.
1185 File contents will be overwritten with those contained in the
1186 work tree's base commit.
1187 There is no way to bring discarded changes back after
1190 If a file was added with
1192 it will become an unversioned file again.
1193 If a file was deleted with
1195 it will be restored.
1202 Instead of reverting all changes in files, interactively select or reject
1203 changes to revert based on
1209 (quit reverting this file) responses.
1210 If a file is in modified status, individual patches derived from the
1211 modified file content can be reverted.
1212 Files in added or deleted status may only be reverted in their entirety.
1213 .It Fl F Ar response-script
1221 responses line-by-line from the specified
1223 file instead of prompting interactively.
1225 Permit recursion into directories.
1226 If this option is not specified,
1228 will refuse to run if a specified
1235 .It Cm commit Oo Fl F Ar path Oc Oo Fl m Ar message Oc Oo Fl N Oc Oo Fl S Oc Op Ar path ...
1236 Create a new commit in the repository from changes in a work tree
1237 and use this commit as the new base commit for the work tree.
1240 is specified, commit all changes in the work tree.
1241 Otherwise, commit changes at or within the specified paths.
1243 If changes have been explicitly staged for commit with
1245 only commit staged changes and reject any specified paths which
1246 have not been staged.
1249 opens a temporary file in an editor where a log message can be written
1257 options are used together.
1259 Show the status of each affected file, using the following status codes:
1260 .Bl -column YXZ description
1261 .It M Ta modified file
1262 .It D Ta file was deleted
1263 .It A Ta new file was added
1264 .It m Ta modified file modes (executable bit only)
1267 Files which are not part of the new commit will retain their previously
1268 recorded base commit.
1271 commands may refuse to run while the work tree contains files from
1272 multiple base commits.
1273 The base commit of such a work tree can be made consistent by running
1275 across the entire work tree.
1279 command requires the
1281 environment variable to be set,
1282 unless an author has been configured in
1288 configuration settings can be
1289 obtained from the repository's
1291 file or from Git's global
1300 Use the prepared log message stored in the file found at
1302 when creating the new commit.
1304 opens a temporary file in an editor where the prepared log message can be
1305 reviewed and edited further if needed.
1306 Cannot be used together with the
1310 Use the specified log message when creating the new commit.
1311 Cannot be used together with the
1315 This option prevents
1317 from opening the commit message in an editor.
1318 It has no effect unless it is used together with the
1320 option and is intended for non-interactive use such as scripting.
1322 Allow the addition of symbolic links which point outside of the path space
1323 that is under version control.
1326 will reject such symbolic links due to safety concerns.
1329 may decide to represent such a symbolic link as a regular file which contains
1330 the link's target path, rather than creating an actual symbolic link which
1331 points outside of the work tree.
1332 Use of this option is discouraged because external mechanisms such as
1334 are better suited for managing symbolic links to paths not under
1339 will refuse to run if certain preconditions are not met.
1340 If the work tree's current branch is not in the
1342 reference namespace, new commits may not be created on this branch.
1343 Local changes may only be committed if they are based on file content
1344 found in the most recent commit on the work tree's branch.
1345 If a path is found to be out of date,
1347 must be used first in order to merge local changes with changes made
1352 .It Cm cherrypick Ar commit
1353 Merge changes from a single
1358 must be on a different branch than the work tree's base commit.
1359 The expected argument is a reference or a commit ID SHA1 hash.
1360 An abbreviated hash argument will be expanded to a full SHA1 hash
1361 automatically, provided the abbreviation is unique.
1363 Show the status of each affected file, using the following status codes:
1364 .Bl -column YXZ description
1365 .It G Ta file was merged
1366 .It C Ta file was merged and conflicts occurred during merge
1367 .It ! Ta changes destined for a missing file were not merged
1368 .It D Ta file was deleted
1369 .It d Ta file's deletion was obstructed by local modifications
1370 .It A Ta new file was added
1371 .It \(a~ Ta changes destined for a non-regular file were not merged
1372 .It ? Ta changes destined for an unversioned file were not merged
1375 The merged changes will appear as local changes in the work tree, which
1378 amended manually or with further
1383 or discarded again with
1387 will refuse to run if certain preconditions are not met.
1388 If the work tree contains multiple base commits it must first be updated
1389 to a single base commit with
1391 If the work tree already contains files with merge conflicts, these
1392 conflicts must be resolved first.
1396 .It Cm backout Ar commit
1397 Reverse-merge changes from a single
1402 must be on the same branch as the work tree's base commit.
1403 The expected argument is a reference or a commit ID SHA1 hash.
1404 An abbreviated hash argument will be expanded to a full SHA1 hash
1405 automatically, provided the abbreviation is unique.
1407 Show the status of each affected file, using the following status codes:
1408 .Bl -column YXZ description
1409 .It G Ta file was merged
1410 .It C Ta file was merged and conflicts occurred during merge
1411 .It ! Ta changes destined for a missing file were not merged
1412 .It D Ta file was deleted
1413 .It d Ta file's deletion was obstructed by local modifications
1414 .It A Ta new file was added
1415 .It \(a~ Ta changes destined for a non-regular file were not merged
1416 .It ? Ta changes destined for an unversioned file were not merged
1419 The reverse-merged changes will appear as local changes in the work tree,
1420 which may be viewed with
1422 amended manually or with further
1427 or discarded again with
1431 will refuse to run if certain preconditions are not met.
1432 If the work tree contains multiple base commits it must first be updated
1433 to a single base commit with
1435 If the work tree already contains files with merge conflicts, these
1436 conflicts must be resolved first.
1440 .It Cm rebase Oo Fl a Oc Oo Fl c Oc Oo Fl l Oc Oo Fl X Oc Op Ar branch
1441 Rebase commits on the specified
1443 onto the tip of the current branch of the work tree.
1446 must share common ancestry with the work tree's current branch.
1447 Rebasing begins with the first descendant commit of the youngest
1448 common ancestor commit shared by the specified
1450 and the work tree's current branch, and stops once the tip commit
1457 is used as intended, the specified
1459 represents a local commit history and may already contain changes
1460 that are not yet visible in any other repositories.
1461 The work tree's current branch, which must be set with
1465 operation, represents a branch from a remote repository which shares
1466 a common history with the specified
1468 but has progressed, and perhaps diverged, due to commits added to the
1471 Rebased commits are accumulated on a temporary branch which the work tree
1472 will remain switched to throughout the entire rebase operation.
1473 Commits on this branch represent the same changes with the same log
1474 messages as their counterparts on the original
1476 but with different commit IDs.
1477 Once rebasing has completed successfully, the temporary branch becomes
1478 the new version of the specified
1480 and the work tree is automatically switched to it.
1482 Old commits in their pre-rebase state are automatically backed up in the
1483 .Dq refs/got/backup/rebase
1484 reference namespace.
1485 As long as these references are not removed older versions of rebased
1486 commits will remain in the repository and can be viewed with the
1489 Removal of these references makes objects which become unreachable via
1490 any reference subject to removal by Git's garbage collector or
1491 .Cm gotadmin cleanup .
1493 While rebasing commits, show the status of each affected file,
1494 using the following status codes:
1495 .Bl -column YXZ description
1496 .It G Ta file was merged
1497 .It C Ta file was merged and conflicts occurred during merge
1498 .It ! Ta changes destined for a missing file were not merged
1499 .It D Ta file was deleted
1500 .It d Ta file's deletion was obstructed by local modifications
1501 .It A Ta new file was added
1502 .It \(a~ Ta changes destined for a non-regular file were not merged
1503 .It ? Ta changes destined for an unversioned file were not merged
1506 If merge conflicts occur the rebase operation is interrupted and may
1507 be continued once conflicts have been resolved.
1508 Alternatively, the rebase operation may be aborted which will leave
1510 unmodified and the work tree switched back to its original branch.
1512 If a merge conflict is resolved in a way which renders the merged
1513 change into a no-op change, the corresponding commit will be elided
1514 when the rebase operation continues.
1517 will refuse to run if certain preconditions are not met.
1518 If the work tree is not yet fully updated to the tip commit of its
1519 branch then the work tree must first be updated with
1521 If changes have been staged with
1523 these changes must first be committed with
1527 If the work tree contains local changes, these changes must first be
1534 contains changes to files outside of the work tree's path prefix,
1535 the work tree cannot be used to rebase this branch.
1541 commands will refuse to run while a rebase operation is in progress.
1542 Other commands which manipulate the work tree may be used for
1543 conflict resolution purposes.
1550 Abort an interrupted rebase operation.
1551 If this option is used, no other command-line arguments are allowed.
1553 Continue an interrupted rebase operation.
1554 If this option is used, no other command-line arguments are allowed.
1556 Show a list of past rebase operations, represented by references in the
1557 .Dq refs/got/backup/rebase
1558 reference namespace.
1560 Display the author, date, and log message of each backed up commit,
1561 the object ID of the corresponding post-rebase commit, and
1562 the object ID of their common ancestor commit.
1563 Given these object IDs,
1570 options can be used to examine the history of either version of the branch,
1575 option can be used to create a new branch from a pre-rebase state if desired.
1579 is specified, only show commits which at some point in time represented this
1581 Otherwise, list all backed up commits for any branches.
1583 If this option is used,
1585 does not require a work tree.
1586 None of the other options can be used together with
1589 Delete backups created by past rebase operations, represented by references
1591 .Dq refs/got/backup/rebase
1592 reference namespace.
1596 is specified, only delete backups which at some point in time represented
1598 Otherwise, delete all references found within
1599 .Dq refs/got/backup/rebase .
1601 Any commit, tree, tag, and blob objects belonging to deleted backups
1602 remain in the repository and may be removed separately with
1603 Git's garbage collector or
1604 .Cm gotadmin cleanup .
1606 If this option is used,
1608 does not require a work tree.
1609 None of the other options can be used together with
1615 .It Cm histedit Oo Fl a Oc Oo Fl c Oc Oo Fl f Oc Oo Fl F Ar histedit-script Oc Oo Fl m Oc Oo Fl l Oc Oo Fl X Oc Op Ar branch
1616 Edit commit history between the work tree's current base commit and
1617 the tip commit of the work tree's current branch.
1621 operation the work tree's current branch must be set with
1623 to the branch which should be edited, unless this branch is already the
1624 current branch of the work tree.
1625 The tip of this branch represents the upper bound (inclusive) of commits
1630 Furthermore, the work tree's base commit
1633 to a point in this branch's commit history where editing should begin.
1634 This commit represents the lower bound (non-inclusive) of commits touched
1639 Editing of commit history is controlled via a
1641 which can be written in an editor based on a template, passed on the
1642 command line, or generated with the
1648 The format of the histedit script is line-based.
1649 Each line in the script begins with a command name, followed by
1650 whitespace and an argument.
1651 For most commands, the expected argument is a commit ID SHA1 hash.
1652 Any remaining text on the line is ignored.
1653 Lines which begin with the
1655 character are ignored entirely.
1657 The available commands are as follows:
1658 .Bl -column YXZ pick-commit
1659 .It pick Ar commit Ta Use the specified commit as it is.
1660 .It edit Ar commit Ta Use the specified commit but once changes have been
1661 merged into the work tree interrupt the histedit operation for amending.
1662 .It fold Ar commit Ta Combine the specified commit with the next commit
1663 listed further below that will be used.
1664 .It drop Ar commit Ta Remove this commit from the edited history.
1665 .It mesg Ar log-message Ta Use the specified single-line log message for
1666 the commit on the previous line.
1667 If the log message argument is left empty, open an editor where a new
1668 log message can be written.
1671 Every commit in the history being edited must be mentioned in the script.
1672 Lines may be re-ordered to change the order of commits in the edited history.
1673 No commit may be listed more than once.
1675 Edited commits are accumulated on a temporary branch which the work tree
1676 will remain switched to throughout the entire histedit operation.
1677 Once history editing has completed successfully, the temporary branch becomes
1678 the new version of the work tree's branch and the work tree is automatically
1681 Old commits in their pre-histedit state are automatically backed up in the
1682 .Dq refs/got/backup/histedit
1683 reference namespace.
1684 As long as these references are not removed older versions of edited
1685 commits will remain in the repository and can be viewed with the
1688 Removal of these references makes objects which become unreachable via
1689 any reference subject to removal by Git's garbage collector or
1690 .Cm gotadmin cleanup .
1692 While merging commits, show the status of each affected file,
1693 using the following status codes:
1694 .Bl -column YXZ description
1695 .It G Ta file was merged
1696 .It C Ta file was merged and conflicts occurred during merge
1697 .It ! Ta changes destined for a missing file were not merged
1698 .It D Ta file was deleted
1699 .It d Ta file's deletion was obstructed by local modifications
1700 .It A Ta new file was added
1701 .It \(a~ Ta changes destined for a non-regular file were not merged
1702 .It ? Ta changes destined for an unversioned file were not merged
1705 If merge conflicts occur the histedit operation is interrupted and may
1706 be continued once conflicts have been resolved.
1707 Alternatively, the histedit operation may be aborted which will leave
1708 the work tree switched back to its original branch.
1710 If a merge conflict is resolved in a way which renders the merged
1711 change into a no-op change, the corresponding commit will be elided
1712 when the histedit operation continues.
1715 will refuse to run if certain preconditions are not met.
1716 If the work tree's current branch is not in the
1718 reference namespace, the history of the branch may not be edited.
1719 If the work tree contains multiple base commits it must first be updated
1720 to a single base commit with
1722 If changes have been staged with
1724 these changes must first be committed with
1728 If the work tree contains local changes, these changes must first be
1733 If the edited history contains changes to files outside of the work tree's
1734 path prefix, the work tree cannot be used to edit the history of this branch.
1741 commands will refuse to run while a histedit operation is in progress.
1742 Other commands which manipulate the work tree may be used, and the
1744 command may be used to commit arbitrary changes to the temporary branch
1745 while the histedit operation is interrupted.
1752 Abort an interrupted histedit operation.
1753 If this option is used, no other command-line arguments are allowed.
1755 Continue an interrupted histedit operation.
1756 If this option is used, no other command-line arguments are allowed.
1758 Fold all commits into a single commit.
1759 This option is a quick equivalent to a histedit script which folds all
1760 commits, combining them all into one commit.
1763 option can only be used when starting a new histedit operation.
1764 If this option is used, no other command-line arguments are allowed.
1765 .It Fl F Ar histedit-script
1768 instead of opening a temporary file in an editor where a histedit script
1771 Edit log messages only.
1772 This option is a quick equivalent to a histedit script which edits
1773 only log messages but otherwise leaves every picked commit as-is.
1776 option can only be used when starting a new histedit operation.
1777 If this option is used, no other command-line arguments are allowed.
1779 Show a list of past histedit operations, represented by references in the
1780 .Dq refs/got/backup/histedit
1781 reference namespace.
1783 Display the author, date, and log message of each backed up commit,
1784 the object ID of the corresponding post-histedit commit, and
1785 the object ID of their common ancestor commit.
1786 Given these object IDs,
1793 options can be used to examine the history of either version of the branch,
1798 option can be used to create a new branch from a pre-histedit state if desired.
1802 is specified, only show commits which at some point in time represented this
1804 Otherwise, list all backed up commits for any branches.
1806 If this option is used,
1808 does not require a work tree.
1809 None of the other options can be used together with
1812 Delete backups created by past histedit operations, represented by references
1814 .Dq refs/got/backup/histedit
1815 reference namespace.
1819 is specified, only delete backups which at some point in time represented
1821 Otherwise, delete all references found within
1822 .Dq refs/got/backup/histedit .
1824 Any commit, tree, tag, and blob objects belonging to deleted backups
1825 remain in the repository and may be removed separately with
1826 Git's garbage collector or
1827 .Cm gotadmin cleanup .
1829 If this option is used,
1831 does not require a work tree.
1832 None of the other options can be used together with
1838 .It Cm integrate Ar branch
1839 Integrate the specified
1841 into the work tree's current branch.
1842 Files in the work tree are updated to match the contents on the integrated
1844 and the reference of the work tree's branch is changed to point at the
1845 head commit of the integrated
1848 Both branches can be considered equivalent after integration since they
1849 will be pointing at the same commit.
1850 Both branches remain available for future work, if desired.
1851 In case the integrated
1853 is no longer needed it may be deleted with
1856 Show the status of each affected file, using the following status codes:
1857 .Bl -column YXZ description
1858 .It U Ta file was updated
1859 .It D Ta file was deleted
1860 .It A Ta new file was added
1861 .It \(a~ Ta versioned file is obstructed by a non-regular file
1862 .It ! Ta a missing versioned file was restored
1866 will refuse to run if certain preconditions are not met.
1867 Most importantly, the
1869 must have been rebased onto the work tree's current branch with
1871 before it can be integrated, in order to linearize commit history and
1872 resolve merge conflicts.
1873 If the work tree contains multiple base commits it must first be updated
1874 to a single base commit with
1876 If changes have been staged with
1878 these changes must first be committed with
1882 If the work tree contains local changes, these changes must first be
1890 .It Cm stage Oo Fl l Oc Oo Fl p Oc Oo Fl F Ar response-script Oc Oo Fl S Oc Op Ar path ...
1891 Stage local changes for inclusion in the next commit.
1894 is specified, stage all changes in the work tree.
1895 Otherwise, stage changes at or within the specified paths.
1896 Paths may be staged if they are added, modified, or deleted according to
1899 Show the status of each affected file, using the following status codes:
1900 .Bl -column YXZ description
1901 .It A Ta file addition has been staged
1902 .It M Ta file modification has been staged
1903 .It D Ta file deletion has been staged
1906 Staged file contents are saved in newly created blob objects in the repository.
1907 These blobs will be referred to by tree objects once staged changes have been
1910 Staged changes affect the behaviour of
1915 While paths with staged changes exist, the
1917 command will refuse to commit any paths which do not have staged changes.
1918 Local changes created on top of staged changes can only be committed if
1919 the path is staged again, or if the staged changes are committed first.
1922 command will show both local changes and staged changes.
1925 command is able to display local changes relative to staged changes,
1926 and to display staged changes relative to the repository.
1929 command cannot revert staged changes but may be used to revert
1930 local changes created on top of staged changes.
1937 Instead of staging new changes, list paths which are already staged,
1938 along with the IDs of staged blob objects and stage status codes.
1939 If paths were provided in the command line show the staged paths
1940 among the specified paths.
1941 Otherwise, show all staged paths.
1943 Instead of staging the entire content of a changed file, interactively
1944 select or reject changes for staging based on
1948 (reject change), and
1950 (quit staging this file) responses.
1951 If a file is in modified status, individual patches derived from the
1952 modified file content can be staged.
1953 Files in added or deleted status may only be staged or rejected in
1955 .It Fl F Ar response-script
1963 responses line-by-line from the specified
1965 file instead of prompting interactively.
1967 Allow staging of symbolic links which point outside of the path space
1968 that is under version control.
1971 will reject such symbolic links due to safety concerns.
1974 may decide to represent such a symbolic link as a regular file which contains
1975 the link's target path, rather than creating an actual symbolic link which
1976 points outside of the work tree.
1977 Use of this option is discouraged because external mechanisms such as
1979 are better suited for managing symbolic links to paths not under
1984 will refuse to run if certain preconditions are not met.
1985 If a file contains merge conflicts, these conflicts must be resolved first.
1986 If a file is found to be out of date relative to the head commit on the
1987 work tree's current branch, the file must be updated with
1989 before it can be staged (however, this does not prevent the file from
1990 becoming out-of-date at some point after having been staged).
1997 commands will refuse to run while staged changes exist.
1998 If staged changes cannot be committed because a staged path
1999 is out of date, the path must be unstaged with
2001 before it can be updated with
2003 and may then be staged again if necessary.
2007 .It Cm unstage Oo Fl p Oc Oo Fl F Ar response-script Oc Op Ar path ...
2008 Merge staged changes back into the work tree and put affected paths
2009 back into non-staged status.
2012 is specified, unstage all staged changes across the entire work tree.
2013 Otherwise, unstage changes at or within the specified paths.
2015 Show the status of each affected file, using the following status codes:
2016 .Bl -column YXZ description
2017 .It G Ta file was unstaged
2018 .It C Ta file was unstaged and conflicts occurred during merge
2019 .It ! Ta changes destined for a missing file were not merged
2020 .It D Ta file was staged as deleted and still is deleted
2021 .It d Ta file's deletion was obstructed by local modifications
2022 .It \(a~ Ta changes destined for a non-regular file were not merged
2030 Instead of unstaging the entire content of a changed file, interactively
2031 select or reject changes for unstaging based on
2035 (keep change staged), and
2037 (quit unstaging this file) responses.
2038 If a file is staged in modified status, individual patches derived from the
2039 staged file content can be unstaged.
2040 Files staged in added or deleted status may only be unstaged in their entirety.
2041 .It Fl F Ar response-script
2049 responses line-by-line from the specified
2051 file instead of prompting interactively.
2056 .It Cm cat Oo Fl c Ar commit Oc Oo Fl r Ar repository-path Oc Oo Fl P Oc Ar arg ...
2057 Parse and print contents of objects to standard output in a line-based
2059 Content of commit, tree, and tag objects is printed in a way similar
2060 to the actual content stored in such objects.
2061 Blob object contents are printed as they would appear in files on disk.
2063 Attempt to interpret each argument as a reference, a tag name, or
2064 an object ID SHA1 hash.
2065 References will be resolved to an object ID.
2066 Tag names will resolved to a tag object.
2067 An abbreviated hash argument will be expanded to a full SHA1 hash
2068 automatically, provided the abbreviation is unique.
2070 If none of the above interpretations produce a valid result, or if the
2072 option is used, attempt to interpret the argument as a path which will
2073 be resolved to the ID of an object found at this path in the repository.
2080 Look up paths in the specified
2082 If this option is not used, paths are looked up in the commit resolved
2083 via the repository's HEAD reference.
2084 The expected argument is a commit ID SHA1 hash or an existing reference
2085 or tag name which will be resolved to a commit ID.
2086 An abbreviated hash argument will be expanded to a full SHA1 hash
2087 automatically, provided the abbreviation is unique.
2088 .It Fl r Ar repository-path
2089 Use the repository at the specified path.
2090 If not specified, assume the repository is located at or above the current
2092 If this directory is a
2094 work tree, use the repository path associated with this work tree.
2096 Interpret all arguments as paths only.
2097 This option can be used to resolve ambiguity in cases where paths
2098 look like tag names, reference names, or object IDs.
2100 .It Cm info Op Ar path ...
2101 Display meta-data stored in a work tree.
2106 The work tree to use is resolved implicitly by walking upwards from the
2107 current working directory.
2111 arguments are specified, show additional per-file information for tracked
2112 files located at or within these paths.
2115 argument corresponds to the work tree's root directory, display information
2116 for all tracked files.
2119 .Bl -tag -width GOT_AUTHOR
2121 The author's name and email address for
2126 .Dq An Flan Hacker Aq Mt flan_hacker@openbsd.org .
2129 may fail to parse commits without an email address in author data,
2133 environment variables with a missing email address.
2135 .Ev GOT_AUTHOR will be overriden by configuration settings in
2141 configuration settings in the repository's
2148 configuration settings contained in Git's global
2150 configuration file will only be used if neither
2154 environment variable provide author information.
2155 .It Ev VISUAL , EDITOR
2156 The editor spawned by
2164 text editor will be spawned in order to give
2166 the attention it deserves.
2167 .It Ev GOT_LOG_DEFAULT_LIMIT
2168 The default limit on the number of commits traversed by
2170 If set to zero, the limit is unbounded.
2171 This variable will be silently ignored if it is set to a non-numeric value.
2174 .Bl -tag -width packed-refs -compact
2176 Repository-wide configuration settings for
2180 configuration file located in the root directory of a Git repository
2181 supersedes any relevant settings in Git's
2185 .It Pa .got/got.conf
2186 Worktree-specific configuration settings for
2190 configuration file in the
2192 meta-data directory of a work tree supersedes any relevant settings in
2195 configuration file and Git's
2202 Clone an existing Git repository for use with
2206 .Dl $ got clone ssh://git@github.com/openbsd/src.git
2208 Use of HTTP URLs currently requires
2212 .Dl $ git clone --bare https://github.com/openbsd/src.git
2214 Alternatively, for quick and dirty local testing of
2216 a new Git repository could be created and populated with files,
2217 e.g. from a temporary CVS checkout located at
2220 .Dl $ got init /var/git/src.git
2221 .Dl $ got import -r /var/git/src.git -I CVS -I obj /tmp/src
2223 Check out a work tree from the Git repository to /usr/src:
2225 .Dl $ got checkout /var/git/src.git /usr/src
2227 View local changes in a work tree directory:
2229 .Dl $ got diff | less
2231 In a work tree, display files in a potentially problematic state:
2233 .Dl $ got status -s 'C!~?'
2235 Interactively revert selected local changes in a work tree directory:
2237 .Dl $ got revert -p -R\ .
2239 In a work tree or a git repository directory, list all branch references:
2243 In a work tree or a git repository directory, create a new branch called
2244 .Dq unified-buffer-cache
2245 which is forked off the
2249 .Dl $ got branch -c master unified-buffer-cache
2251 Switch an existing work tree to the branch
2252 .Dq unified-buffer-cache .
2253 Local changes in the work tree will be preserved and merged if necessary:
2255 .Dl $ got update -b unified-buffer-cache
2257 Create a new commit from local changes in a work tree directory.
2258 This new commit will become the head commit of the work tree's current branch:
2262 In a work tree or a git repository directory, view changes committed in
2263 the 3 most recent commits to the work tree's branch, or the branch resolved
2264 via the repository's HEAD reference, respectively:
2266 .Dl $ got log -p -l 3
2268 As above, but display changes in the order in which
2270 could apply them in sequence:
2272 .Dl $ got log -p -l 3 -R
2274 In a work tree or a git repository directory, log the history of a subdirectory:
2276 .Dl $ got log sys/uvm
2278 While operating inside a work tree, paths are specified relative to the current
2279 working directory, so this command will log the subdirectory
2282 .Dl $ cd sys/uvm && got log\ .
2284 And this command has the same effect:
2286 .Dl $ cd sys/dev/usb && got log ../../uvm
2288 And this command displays work tree meta-data about all tracked files:
2291 .Dl $ got info\ . | less
2293 Add new files and remove obsolete files in a work tree directory:
2295 .Dl $ got add sys/uvm/uvm_ubc.c
2296 .Dl $ got remove sys/uvm/uvm_vnode.c
2298 Create a new commit from local changes in a work tree directory
2299 with a pre-defined log message.
2301 .Dl $ got commit -m 'unify the buffer cache'
2303 Alternatively, create a new commit from local changes in a work tree
2304 directory with a log message that has been prepared in the file
2307 .Dl $ got commit -F /tmp/msg
2309 Update any work tree checked out from the
2310 .Dq unified-buffer-cache
2311 branch to the latest commit on this branch:
2315 Roll file content on the unified-buffer-cache branch back by one commit,
2316 and then fetch the rolled-back change into the work tree as a local change
2317 to be amended and perhaps committed again:
2319 .Dl $ got backout unified-buffer-cache
2320 .Dl $ got commit -m 'roll back previous'
2321 .Dl $ # now back out the previous backout :-)
2322 .Dl $ got backout unified-buffer-cache
2324 Fetch new upstream commits into the local repository's
2331 In a repository created with a HTTP URL and
2332 .Cm git clone --bare
2335 command must be used instead:
2337 .Dl $ cd /var/git/src.git
2338 .Dl $ git fetch origin master:refs/remotes/origin/master
2342 branch to merge the new changes that are now visible on the
2347 .Dl $ got update -b origin/master
2348 .Dl $ got rebase master
2351 .Dq unified-buffer-cache
2352 branch on top of the new head commit of the
2356 .Dl $ got update -b master
2357 .Dl $ got rebase unified-buffer-cache
2359 Create a patch from all changes on the unified-buffer-cache branch.
2360 The patch can be mailed out for review and applied to
2364 .Dl $ got diff master unified-buffer-cache > /tmp/ubc.diff
2366 Edit the entire commit history of the
2367 .Dq unified-buffer-cache
2370 .Dl $ got update -b unified-buffer-cache
2371 .Dl $ got update -c master
2374 In order to merge changes committed to the
2375 .Dq unified-buffer-cache
2376 branch back into the
2379 .Dq unified-buffer-cache
2380 branch must first be rebased onto the
2384 .Dl $ got update -b master
2385 .Dl $ got rebase unified-buffer-cache
2388 .Dq unified-buffer-cache
2389 branch can now be made visible on the
2393 Because the rebase operation switched the work tree to the
2394 .Dq unified-buffer-cache
2395 branch, the work tree must be switched back to the
2398 .Dq unified-buffer-cache
2399 branch can be integrated into
2402 .Dl $ got update -b master
2403 .Dl $ got integrate unified-buffer-cache
2405 Additional steps may be necessary if local changes need to be pushed back
2406 to the remote repository, which currently requires
2408 Before working against existing branches in a repository cloned with
2409 .Cm git clone --bare
2414 must be configured to map all references in the remote repository
2417 namespace of the local repository.
2418 This can be achieved by setting Git's
2419 .Pa remote.origin.fetch
2420 configuration variable to the value
2421 .Dq +refs/heads/*:refs/remotes/origin/*
2426 .Dl $ cd /var/git/repo
2427 .Dl $ git config remote.origin.fetch '+refs/heads/*:refs/remotes/origin/*'
2431 option must be disabled:
2433 .Dl $ cd /var/git/repo
2434 .Dl $ git config remote.origin.mirror false
2436 Alternatively, the following
2438 configuration item can be added manually to the Git repository's
2442 .Dl [remote \&"origin\&"]
2444 .Dl fetch = +refs/heads/*:refs/remotes/origin/*
2447 This configuration leaves the local repository's
2449 namespace free for use by local branches checked out with
2451 and, if needed, created with
2456 namespace can now be updated with incoming changes from the remote
2461 without extra command line arguments:
2463 .Dl $ cd /var/git/repo
2466 To make changes fetched from the remote repository appear on the
2470 branch must be rebased onto the
2473 This will also merge local changes, if any, with the incoming changes:
2475 .Dl $ got update -b origin/master
2476 .Dl $ got rebase master
2480 branch, log messages for local changes can now be amended with
2482 by other developers and any other important new information:
2484 .Dl $ got update -c origin/master
2485 .Dl $ got histedit -m
2487 Local changes on the
2489 branch can then be pushed to the remote
2493 .Dl $ cd /var/git/repo
2494 .Dl $ git push origin master
2498 .Xr git-repository 5 ,
2499 .Xr got-worktree 5 ,
2502 .An Stefan Sperling Aq Mt stsp@openbsd.org
2503 .An Martin Pieuchot Aq Mt mpi@openbsd.org
2504 .An Joshua Stein Aq Mt jcs@openbsd.org
2505 .An Ori Bernstein Aq Mt ori@openbsd.org
2508 is a work-in-progress and some features remain to be implemented.
2510 At present, the user has to fall back on
2512 to perform some tasks.
2516 Reading from remote repositories over HTTP or HTTPS protocols requires
2521 Writing to remote repositories, over any protocol, requires
2524 The creation of merge commits, i.e. commits with two or more parent commits,
2528 In situations where files or directories were moved around
2530 will not automatically merge changes to new locations and
2532 will usually produce better results.
