2 .\" Copyright (c) 2017 Martin Pieuchot
3 .\" Copyright (c) 2018, 2019 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
79 .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
80 Create an initial commit in a repository from the file hierarchy
83 The created commit will not have any parent commits, i.e. it will be a
85 Also create a new reference which provides a branch name for the newly
87 Show the path of each imported file to indicate progress.
93 environment variable to be set,
98 configuration settings can be obtained from the repository's
100 file or from Git's global
111 instead of creating the default branch
113 Use of this option is required if the
115 branch already exists.
117 Use the specified log message when creating the new commit.
122 opens a temporary file in an editor where a log message can be written.
123 .It Fl r Ar repository-path
124 Use the repository at the specified path.
125 If not specified, assume the repository is located at or above the current
128 Ignore files or directories with a name which matches the specified
130 This option may be specified multiple times to build a list of ignore patterns.
133 follows the globbing rules documented in
139 .It Cm checkout 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
140 Copy files from a repository into a new work tree.
143 is not specified, either use the last component of
144 .Ar repository path ,
147 was specified use the last component of
155 Check out files from a commit on the specified
157 If this option is not specified, a branch resolved via the repository's HEAD
158 reference will be used.
160 Check out files from the specified
162 on the selected branch.
163 The expected argument is a commit ID SHA1 hash or an existing reference
164 or tag name which will be resolved to a commit ID.
165 An abbreviated hash argument will be expanded to a full SHA1 hash
166 automatically, provided the abbreviation is unique.
167 If this option is not specified, the most recent commit on the selected
169 .It Fl p Ar path-prefix
170 Restrict the work tree to a subset of the repository's tree hierarchy.
171 Only files beneath the specified
178 .It Cm update Oo Fl b Ar branch Oc Oo Fl c Ar commit Oc Op Ar path ...
179 Update an existing work tree to a different commit.
180 Show the status of each affected file, using the following status codes:
181 .Bl -column YXZ description
182 .It U Ta file was updated and contained no local changes
183 .It G Ta file was updated and local changes were merged cleanly
184 .It C Ta file was updated and conflicts occurred during merge
185 .It D Ta file was deleted
186 .It A Ta new file was added
187 .It \(a~ Ta versioned file is obstructed by a non-regular file
188 .It ! Ta a missing versioned file was restored
193 is specified, update the entire work tree.
194 Otherwise, restrict the update operation to files at or within the
196 Each path is required to exist in the update operation's target commit.
197 Files in the work tree outside specified paths will remain unchanged and
198 will retain their previously recorded base commit.
201 commands may refuse to run while the work tree contains files from
202 multiple base commits.
203 The base commit of such a work tree can be made consistent by running
205 across the entire work tree.
208 is incompatible with the
213 cannot update paths with staged changes.
214 If changes have been staged with
216 these changes must first be committed with
226 Switch the work tree's branch reference to the specified
228 before updating the work tree.
229 This option requires that all paths in the work tree are updated.
231 Update the work tree to the specified
233 The expected argument is a commit ID SHA1 hash or an existing reference
234 or tag name which will be resolved to a commit ID.
235 An abbreviated hash argument will be expanded to a full SHA1 hash
236 automatically, provided the abbreviation is unique.
237 If this option is not specified, the most recent commit on the work tree's
243 .It Cm status Op Ar path ...
244 Show the current modification status of files in a work tree,
245 using the following status codes:
246 .Bl -column YXZ description
247 .It M Ta modified file
248 .It A Ta file scheduled for addition in next commit
249 .It D Ta file scheduled for deletion in next commit
250 .It C Ta modified or added file which contains merge conflicts
251 .It ! Ta versioned file was expected on disk but is missing
252 .It \(a~ Ta versioned file is obstructed by a non-regular file
253 .It ? Ta unversioned item not tracked by
255 .It m Ta modified file modes (executable bit only)
256 .It N Ta non-existent
258 specified on the command line
263 is specified, show modifications in the entire work tree.
264 Otherwise, show modifications at or within the specified paths.
266 If changes have been staged with
268 staged changes are shown in the second output column, using the following
270 .Bl -column YXZ description
271 .It M Ta file modification is staged
272 .It A Ta file addition is staged
273 .It D Ta file deletion is staged
276 Changes created on top of staged changes are indicated in the first column:
277 .Bl -column YXZ description
278 .It MM Ta file was modified after earlier changes have been staged
279 .It MA Ta file was modified after having been staged for addition
282 For compatibility with
293 files in each traversed directory and will not display unversioned files
294 which match these patterns.
299 supports consecutive asterisks,
301 which will match an arbitrary amount of directories.
305 only supports a single ignore pattern per line.
309 does not support negated ignore patterns prefixed with
311 and gives no special significance to the location of path component separators,
317 .It Cm log Oo Fl c Ar commit Oc Oo Fl C Ar number Oc Oo Fl f Oc Oo Fl l Ar N Oc Oo Fl p Oc Oo Fl g Ar search-pattern Oc Oo Fl r Ar repository-path Oc Op Ar path
318 Display history of a repository.
321 is specified, show only commits which modified this path.
328 Start traversing history at the specified
330 The expected argument is a commit ID SHA1 hash or an existing reference
331 or tag name which will be resolved to a commit ID.
332 An abbreviated hash argument will be expanded to a full SHA1 hash
333 automatically, provided the abbreviation is unique.
334 If this option is not specified, default to the work tree's current branch
335 if invoked in a work tree, or to the repository's HEAD reference.
337 Set the number of context lines shown in diffs with
339 By default, 3 lines of context are shown.
341 Restrict history traversal to the first parent of each commit.
342 This shows the linear history of the current branch only.
343 Merge commits which affected the current branch will be shown but
344 individual commits which originated on other branches will be omitted.
346 Limit history traversal to a given number of commits.
347 If this option is not specified, a default limit value of zero is used,
348 which is treated as an unbounded limit.
350 .Ev GOT_LOG_DEFAULT_LIMIT
351 environment variable may be set to change this default value.
353 Display the patch of modifications made in each commit.
356 is specified, only show the patch of modifications at or within this path.
357 .It Fl g Ar search-pattern
358 If specified, show only commits which log message matches the extended
361 Regular expression syntax is documented in
363 .It Fl r Ar repository-path
364 Use the repository at the specified path.
365 If not specified, assume the repository is located at or above the current
367 If this directory is a
369 work tree, use the repository path associated with this work tree.
371 .It Cm diff 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
372 When invoked within a work tree with less than two arguments, display
373 uncommitted changes in the work tree.
376 is specified, only show changes within this path.
378 If two arguments are provided, treat each argument as a reference, a tag
379 name, or an object ID SHA1 hash, and display differences between the
380 corresponding objects.
381 Both objects must be of the same type (blobs, trees, or commits).
382 An abbreviated hash argument will be expanded to a full SHA1 hash
383 automatically, provided the abbreviation is unique.
390 Set the number of context lines shown in the diff.
391 By default, 3 lines of context are shown.
392 .It Fl r Ar repository-path
393 Use the repository at the specified path.
394 If not specified, assume the repository is located at or above the current
396 If this directory is a
398 work tree, use the repository path associated with this work tree.
400 Show changes staged with
402 instead of showing local changes.
403 This option is only valid when
405 is invoked in a work tree.
407 Ignore whitespace-only changes.
412 .It Cm blame Oo Fl c Ar commit Oc Oo Fl r Ar repository-path Oc Ar path
413 Display line-by-line history of a file at the specified path.
420 Start traversing history at the specified
422 The expected argument is a commit ID SHA1 hash or an existing reference
423 or tag name which will be resolved to a commit ID.
424 An abbreviated hash argument will be expanded to a full SHA1 hash
425 automatically, provided the abbreviation is unique.
426 .It Fl r Ar repository-path
427 Use the repository at the specified path.
428 If not specified, assume the repository is located at or above the current
430 If this directory is a
432 work tree, use the repository path associated with this work tree.
437 .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
438 Display a listing of files and directories at the specified
439 directory path in the repository.
440 Entries shown in this listing may carry one of the following trailing
442 .Bl -column YXZ description
443 .It @ Ta entry is a symbolic link
444 .It / Ta entry is a directory
445 .It * Ta entry is an executable file
446 .It $ Ta entry is a Git submodule
451 is specified, list the repository path corresponding to the current
452 directory of the work tree, or the root directory of the repository
453 if there is no work tree.
460 List files and directories as they appear in the specified
462 The expected argument is a commit ID SHA1 hash or an existing reference
463 or tag name which will be resolved to a commit ID.
464 An abbreviated hash argument will be expanded to a full SHA1 hash
465 automatically, provided the abbreviation is unique.
466 .It Fl r Ar repository-path
467 Use the repository at the specified path.
468 If not specified, assume the repository is located at or above the current
470 If this directory is a
472 work tree, use the repository path associated with this work tree.
474 Show object IDs of files (blob objects) and directories (tree objects).
476 Recurse into sub-directories in the repository.
481 .It Cm ref Oo Fl r Ar repository-path Oc Oo Fl l Oc Oo Fl d Ar name Oc Oo Fl s Oc Op Ar name Ar target
482 Manage references in a repository.
484 If no options are passed, expect two arguments and attempt to create,
485 or update, the reference with the given
487 and make it point at the given
489 The name must be an absolute reference name, i.e. it must begin with
491 The target may be an object ID SHA1 hash or an existing reference which
492 will be resolved to an object ID.
493 An abbreviated hash argument will be expanded to a full SHA1 hash
494 automatically, provided the abbreviation is unique.
500 .It Fl r Ar repository-path
501 Use the repository at the specified path.
502 If not specified, assume the repository is located at or above the current
504 If this directory is a
506 work tree, use the repository path associated with this work tree.
508 List all existing references in the repository.
510 Delete the reference with the specified name from the repository.
512 Create a symbolic reference pointing at the specified
514 which must be an existing reference.
515 Care should be taken not to create loops between references when
518 .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 Op Ar name
519 Manage branches in a repository.
521 Branches are managed via references which live in the
526 command operates on references in this namespace only.
528 If invoked in a work tree without any arguments, print the name of the
529 work tree's current branch.
532 argument is passed, attempt to create a branch reference with the given name.
533 By default the new branch reference will point at the latest commit on the
534 work tree's current branch if invoked in a work tree, and otherwise to a commit
535 resolved via the repository's HEAD reference.
542 Make a newly created branch reference point at the specified
546 argument is a commit ID SHA1 hash or an existing reference
547 or tag name which will be resolved to a commit ID.
548 .It Fl r Ar repository-path
549 Use the repository at the specified path.
550 If not specified, assume the repository is located at or above the current
552 If this directory is a
554 work tree, use the repository path associated with this work tree.
556 List all existing branches in the repository.
557 If invoked in a work tree, the work tree's current branch is shown
558 with one the following annotations:
559 .Bl -column YXZ description
560 .It * Ta work tree's base commit matches the branch tip
561 .It \(a~ Ta work tree's base commit is out-of-date
564 Delete the branch with the specified name from the repository.
565 Only the branch reference is deleted.
566 Any commit, tree, and blob objects belonging to the branch
567 remain in the repository and may be removed separately with
568 Git's garbage collector.
573 .It Cm tag Oo Fl m Ar message Oc Oo Fl r Ar repository-path Oc Oo Fl l Oc Ar name Op Ar commit Oc
574 Manage tags in a repository.
576 Tags are managed via references which live in the
581 command operates on references in this namespace only.
582 References in this namespace point at tag objects which contain a pointer
583 to another object, a tag message, as well as author and timestamp information.
585 Expect one or two arguments and attempt to create a tag with the given
587 and make this tag point at the given
589 If no commit is specified, default to the latest commit on the work tree's
590 current branch if invoked in a work tree, and to a commit resolved via
591 the repository's HEAD reference otherwise.
592 Otherwise, the expected argument is a commit ID SHA1 hash or an existing
593 reference or tag name which will be resolved to a commit ID.
594 An abbreviated hash argument will be expanded to a full SHA1 hash
595 automatically, provided the abbreviation is unique.
602 Use the specified tag message when creating the new tag
607 opens a temporary file in an editor where a tag message can be written.
608 .It Fl r Ar repository-path
609 Use the repository at the specified path.
610 If not specified, assume the repository is located at or above the current
612 If this directory is a
614 work tree, use the repository path associated with this work tree.
616 List all existing tags in the repository instead of creating a new tag.
617 If this option is used, no other command-line arguments are allowed.
622 command will not delete tags or change existing tags.
623 If a tag must be deleted, the
625 command may be used to delete a tag's reference.
626 This should only be done if the tag has not already been copied to
628 .It Cm add Oo Fl R Oc Ar path ...
629 Schedule unversioned files in a work tree for addition to the
630 repository in the next commit.
637 Permit recursion into directories.
638 If this option is not specified,
640 will refuse to run if a specified
644 .It Cm remove Ar file-path ...
645 Remove versioned files from a work tree and schedule them for deletion
646 from the repository in the next commit.
653 Perform the operation even if a file contains uncommitted modifications.
658 .It Cm revert Oo Fl p Oc Oo Fl F Ar response-script Oc Oo Fl R Oc Ar path ...
659 Revert any uncommitted changes in files at the specified paths.
660 File contents will be overwritten with those contained in the
661 work tree's base commit.
662 There is no way to bring discarded changes back after
665 If a file was added with
667 it will become an unversioned file again.
668 If a file was deleted with
677 Instead of reverting all changes in files, interactively select or reject
678 changes to revert based on
684 (quit reverting this file) responses.
685 If a file is in modified status, individual patches derived from the
686 modified file content can be reverted.
687 Files in added or deleted status may only be reverted in their entirety.
688 .It Fl F Ar response-script
696 responses line-by-line from the specified
698 file instead of prompting interactively.
700 Permit recursion into directories.
701 If this option is not specified,
703 will refuse to run if a specified
710 .It Cm commit Oo Fl m Ar message Oc Op Ar path ...
711 Create a new commit in the repository from changes in a work tree
712 and use this commit as the new base commit for the work tree.
715 is specified, commit all changes in the work tree.
716 Otherwise, commit changes at or within the specified paths.
718 If changes have been explicitly staged for commit with
720 only commit staged changes and reject any specified paths which
721 have not been staged.
723 Show the status of each affected file, using the following status codes:
724 .Bl -column YXZ description
725 .It M Ta modified file
726 .It D Ta file was deleted
727 .It A Ta new file was added
728 .It m Ta modified file modes (executable bit only)
731 Files which are not part of the new commit will retain their previously
732 recorded base commit.
735 commands may refuse to run while the work tree contains files from
736 multiple base commits.
737 The base commit of such a work tree can be made consistent by running
739 across the entire work tree.
745 environment variable to be set,
750 configuration settings can be
751 obtained from the repository's
753 file or from Git's global
762 Use the specified log message when creating the new commit.
767 opens a temporary file in an editor where a log message can be written.
771 will refuse to run if certain preconditions are not met.
772 If the work tree's current branch is not in the
774 reference namespace, new commits may not be created on this branch.
775 Local changes may only be committed if they are based on file content
776 found in the most recent commit on the work tree's branch.
777 If a path is found to be out of date,
779 must be used first in order to merge local changes with changes made
784 .It Cm cherrypick Ar commit
785 Merge changes from a single
790 must be on a different branch than the work tree's base commit.
791 The expected argument is a reference or a commit ID SHA1 hash.
792 An abbreviated hash argument will be expanded to a full SHA1 hash
793 automatically, provided the abbreviation is unique.
795 Show the status of each affected file, using the following status codes:
796 .Bl -column YXZ description
797 .It G Ta file was merged
798 .It C Ta file was merged and conflicts occurred during merge
799 .It ! Ta changes destined for a missing file were not merged
800 .It D Ta file was deleted
801 .It d Ta file's deletion was obstructed by local modifications
802 .It A Ta new file was added
803 .It \(a~ Ta changes destined for a non-regular file were not merged
806 The merged changes will appear as local changes in the work tree, which
809 amended manually or with further
814 or discarded again with
818 will refuse to run if certain preconditions are not met.
819 If the work tree contains multiple base commits it must first be updated
820 to a single base commit with
822 If the work tree already contains files with merge conflicts, these
823 conflicts must be resolved first.
827 .It Cm backout Ar commit
828 Reverse-merge changes from a single
833 must be on the same branch as the work tree's base commit.
834 The expected argument is a reference or a commit ID SHA1 hash.
835 An abbreviated hash argument will be expanded to a full SHA1 hash
836 automatically, provided the abbreviation is unique.
838 Show the status of each affected file, using the following status codes:
839 .Bl -column YXZ description
840 .It G Ta file was merged
841 .It C Ta file was merged and conflicts occurred during merge
842 .It ! Ta changes destined for a missing file were not merged
843 .It D Ta file was deleted
844 .It d Ta file's deletion was obstructed by local modifications
845 .It A Ta new file was added
846 .It \(a~ Ta changes destined for a non-regular file were not merged
849 The reverse-merged changes will appear as local changes in the work tree,
850 which may be viewed with
852 amended manually or with further
857 or discarded again with
861 will refuse to run if certain preconditions are not met.
862 If the work tree contains multiple base commits it must first be updated
863 to a single base commit with
865 If the work tree already contains files with merge conflicts, these
866 conflicts must be resolved first.
870 .It Cm rebase Oo Fl a Oc Oo Fl c Oc Op Ar branch
871 Rebase commits on the specified
873 onto the tip of the current branch of the work tree.
876 must share common ancestry with the work tree's current branch.
877 Rebasing begins with the first descendant commit of the youngest
878 common ancestor commit shared by the specified
880 and the work tree's current branch, and stops once the tip commit
885 Rebased commits are accumulated on a temporary branch which the work tree
886 will remain switched to throughout the entire rebase operation.
887 Commits on this branch represent the same changes with the same log
888 messages as their counterparts on the original
890 but with different commit IDs.
891 Once rebasing has completed successfully, the temporary branch becomes
892 the new version of the specified
894 and the work tree is automatically switched to it.
896 While rebasing commits, show the status of each affected file,
897 using the following status codes:
898 .Bl -column YXZ description
899 .It G Ta file was merged
900 .It C Ta file was merged and conflicts occurred during merge
901 .It ! Ta changes destined for a missing file were not merged
902 .It D Ta file was deleted
903 .It d Ta file's deletion was obstructed by local modifications
904 .It A Ta new file was added
905 .It \(a~ Ta changes destined for a non-regular file were not merged
908 If merge conflicts occur the rebase operation is interrupted and may
909 be continued once conflicts have been resolved.
910 Alternatively, the rebase operation may be aborted which will leave
912 unmodified and the work tree switched back to its original branch.
914 If a merge conflict is resolved in a way which renders the merged
915 change into a no-op change, the corresponding commit will be elided
916 when the rebase operation continues.
919 will refuse to run if certain preconditions are not met.
920 If the work tree contains multiple base commits it must first be updated
921 to a single base commit with
923 If changes have been staged with
925 these changes must first be committed with
929 If the work tree contains local changes, these changes must first be
936 contains changes to files outside of the work tree's path prefix,
937 the work tree cannot be used to rebase this branch.
943 commands will refuse to run while a rebase operation is in progress.
944 Other commands which manipulate the work tree may be used for
945 conflict resolution purposes.
952 Abort an interrupted rebase operation.
953 If this option is used, no other command-line arguments are allowed.
955 Continue an interrupted rebase operation.
956 If this option is used, no other command-line arguments are allowed.
961 .It Cm histedit Oo Fl a Oc Oo Fl c Oc Op Fl F Ar histedit-script
962 Edit commit history between the work tree's current base commit and
963 the tip commit of the work tree's current branch.
965 Editing of commit history is controlled via a
967 which can be edited interactively or passed on the command line.
968 The format of the histedit script is line-based.
969 Each line in the script begins with a command name, followed by
970 whitespace and an argument.
971 For most commands, the expected argument is a commit ID SHA1 hash.
972 Any remaining text on the line is ignored.
973 Lines which begin with the
975 character are ignored entirely.
977 The available commands are as follows:
978 .Bl -column YXZ pick-commit
979 .It pick Ar commit Ta Use the specified commit as it is.
980 .It edit Ar commit Ta Use the specified commit but once changes have been
981 merged into the work tree interrupt the histedit operation for amending.
982 .It fold Ar commit Ta Combine the specified commit with the next commit
983 listed further below that will be used.
984 .It drop Ar commit Ta Remove this commit from the edited history.
985 .It mesg Ar log-message Ta Use the specified single-line log message for
986 the commit on the previous line.
987 If the log message argument is left empty, open an editor where a new
988 log message can be written.
991 Every commit in the history being edited must be mentioned in the script.
992 Lines may be re-ordered to change the order of commits in the edited history.
994 Edited commits are accumulated on a temporary branch which the work tree
995 will remain switched to throughout the entire histedit operation.
996 Once history editing has completed successfully, the temporary branch becomes
997 the new version of the work tree's branch and the work tree is automatically
1000 While merging commits, show the status of each affected file,
1001 using the following status codes:
1002 .Bl -column YXZ description
1003 .It G Ta file was merged
1004 .It C Ta file was merged and conflicts occurred during merge
1005 .It ! Ta changes destined for a missing file were not merged
1006 .It D Ta file was deleted
1007 .It d Ta file's deletion was obstructed by local modifications
1008 .It A Ta new file was added
1009 .It \(a~ Ta changes destined for a non-regular file were not merged
1012 If merge conflicts occur the histedit operation is interrupted and may
1013 be continued once conflicts have been resolved.
1014 Alternatively, the histedit operation may be aborted which will leave
1015 the work tree switched back to its original branch.
1017 If a merge conflict is resolved in a way which renders the merged
1018 change into a no-op change, the corresponding commit will be elided
1019 when the histedit operation continues.
1022 will refuse to run if certain preconditions are not met.
1023 If the work tree's current branch is not in the
1025 reference namespace, the history of the branch may not be edited.
1026 If the work tree contains multiple base commits it must first be updated
1027 to a single base commit with
1029 If changes have been staged with
1031 these changes must first be committed with
1035 If the work tree contains local changes, these changes must first be
1040 If the edited history contains changes to files outside of the work tree's
1041 path prefix, the work tree cannot be used to edit the history of this branch.
1045 command will refuse to run while a histedit operation is in progress.
1046 Other commands which manipulate the work tree may be used, and the
1048 command may be used to commit arbitrary changes to the temporary branch
1049 while the histedit operation is interrupted.
1056 Abort an interrupted histedit operation.
1057 If this option is used, no other command-line arguments are allowed.
1059 Continue an interrupted histedit operation.
1060 If this option is used, no other command-line arguments are allowed.
1065 .It Cm integrate Ar branch
1066 Integrate the specified
1068 into the work tree's current branch.
1069 Files in the work tree are updated to match the contents on the integrated
1071 and the reference of the work tree's branch is changed to point at the
1072 head commit of the integrated
1075 Both branches can be considered equivalent after integration since they
1076 will be pointing at the same commit.
1077 Both branches remain available for future work, if desired.
1078 In case the integrated
1080 is no longer needed it may be deleted with
1083 Show the status of each affected file, using the following status codes:
1084 .Bl -column YXZ description
1085 .It U Ta file was updated
1086 .It D Ta file was deleted
1087 .It A Ta new file was added
1088 .It \(a~ Ta versioned file is obstructed by a non-regular file
1089 .It ! Ta a missing versioned file was restored
1093 will refuse to run if certain preconditions are not met.
1094 Most importantly, the
1096 must have been rebased onto the work tree's current branch with
1098 before it can be integrated, in order to linearize commit history and
1099 resolve merge conflicts.
1100 If the work tree contains multiple base commits it must first be updated
1101 to a single base commit with
1103 If changes have been staged with
1105 these changes must first be committed with
1109 If the work tree contains local changes, these changes must first be
1117 .It Cm stage Oo Fl l Oc Oo Fl p Oc Oo Fl F Ar response-script Oc Op Ar path ...
1118 Stage local changes for inclusion in the next commit.
1121 is specified, stage all changes in the work tree.
1122 Otherwise, stage changes at or within the specified paths.
1123 Paths may be staged if they are added, modified, or deleted according to
1126 Show the status of each affected file, using the following status codes:
1127 .Bl -column YXZ description
1128 .It A Ta file addition has been staged
1129 .It M Ta file modification has been staged
1130 .It D Ta file deletion has been staged
1133 Staged file contents are saved in newly created blob objects in the repository.
1134 These blobs will be referred to by tree objects once staged changes have been
1137 Staged changes affect the behaviour of
1142 While paths with staged changes exist, the
1144 command will refuse to commit any paths which do not have staged changes.
1145 Local changes created on top of staged changes can only be committed if
1146 the path is staged again, or if the staged changes are committed first.
1149 command will show both local changes and staged changes.
1152 command is able to display local changes relative to staged changes,
1153 and to display staged changes relative to the repository.
1156 command cannot revert staged changes but may be used to revert
1157 local changes created on top of staged changes.
1164 Instead of staging new changes, list paths which are already staged,
1165 along with the IDs of staged blob objects and stage status codes.
1166 If paths were provided in the command line show the staged paths
1167 among the specified paths.
1168 Otherwise, show all staged paths.
1170 Instead of staging the entire content of a changed file, interactively
1171 select or reject changes for staging based on
1175 (reject change), and
1177 (quit staging this file) responses.
1178 If a file is in modified status, individual patches derived from the
1179 modified file content can be staged.
1180 Files in added or deleted status may only be staged or rejected in
1182 .It Fl F Ar response-script
1190 responses line-by-line from the specified
1192 file instead of prompting interactively.
1196 will refuse to run if certain preconditions are not met.
1197 If a file contains merge conflicts, these conflicts must be resolved first.
1198 If a file is found to be out of date relative to the head commit on the
1199 work tree's current branch, the file must be updated with
1201 before it can be staged (however, this does not prevent the file from
1202 becoming out-of-date at some point after having been staged).
1209 commands will refuse to run while staged changes exist.
1210 If staged changes cannot be committed because a staged path
1211 is out of date, the path must be unstaged with
1213 before it can be updated with
1215 and may then be staged again if necessary.
1219 .It Cm unstage Oo Fl p Oc Oo Fl F Ar response-script Oc Op Ar path ...
1220 Merge staged changes back into the work tree and put affected paths
1221 back into non-staged status.
1224 is specified, unstage all staged changes across the entire work tree.
1225 Otherwise, unstage changes at or within the specified paths.
1227 Show the status of each affected file, using the following status codes:
1228 .Bl -column YXZ description
1229 .It G Ta file was unstaged
1230 .It C Ta file was unstaged and conflicts occurred during merge
1231 .It ! Ta changes destined for a missing file were not merged
1232 .It D Ta file was staged as deleted and still is deleted
1233 .It d Ta file's deletion was obstructed by local modifications
1234 .It \(a~ Ta changes destined for a non-regular file were not merged
1242 Instead of unstaging the entire content of a changed file, interactively
1243 select or reject changes for unstaging based on
1247 (keep change staged), and
1249 (quit unstaging this file) responses.
1250 If a file is staged in modified status, individual patches derived from the
1251 staged file content can be unstaged.
1252 Files staged in added or deleted status may only be unstaged in their entirety.
1253 .It Fl F Ar response-script
1261 responses line-by-line from the specified
1263 file instead of prompting interactively.
1268 .It Cm cat Oo Fl c Ar commit Oc Oo Fl r Ar repository-path Oc Oo Fl P Oc Ar arg ...
1269 Parse and print contents of objects to standard output in a line-based
1271 Content of commit, tree, and tag objects is printed in a way similar
1272 to the actual content stored in such objects.
1273 Blob object contents are printed as they would appear in files on disk.
1275 Attempt to interpret each argument as a reference, a tag name, or
1276 an object ID SHA1 hash.
1277 References will be resolved to an object ID.
1278 Tag names will resolved to a tag object.
1279 An abbreviated hash argument will be expanded to a full SHA1 hash
1280 automatically, provided the abbreviation is unique.
1282 If none of the above interpretations produce a valid result, or if the
1284 option is used, attempt to interpret the argument as a path which will
1285 be resolved to the ID of an object found at this path in the repository.
1292 Look up paths in the specified
1294 If this option is not used, paths are looked up in the commit resolved
1295 via the repository's HEAD reference.
1296 The expected argument is a commit ID SHA1 hash or an existing reference
1297 or tag name which will be resolved to a commit ID.
1298 An abbreviated hash argument will be expanded to a full SHA1 hash
1299 automatically, provided the abbreviation is unique.
1300 .It Fl r Ar repository-path
1301 Use the repository at the specified path.
1302 If not specified, assume the repository is located at or above the current
1304 If this directory is a
1306 work tree, use the repository path associated with this work tree.
1308 Interpret all arguments as paths only.
1309 This option can be used to resolve ambiguity in cases where paths
1310 look like tag names, reference names, or object IDs.
1314 .Bl -tag -width GOT_AUTHOR
1316 The author's name and email address for
1321 .Dq An Flan Hacker Aq Mt flan_hacker@openbsd.org .
1324 may fail to parse commits without an email address in author data,
1328 environment variables with a missing email address.
1334 configuration settings in the repository's
1336 file will override the value of
1342 configuration settings contained in Git's global
1344 configuration file will be used only if the
1346 environment variable is
1349 .It Ev VISUAL , EDITOR
1350 The editor spawned by
1355 .It Ev GOT_LOG_DEFAULT_LIMIT
1356 The default limit on the number of commits traversed by
1358 If set to zero, the limit is unbounded.
1359 This variable will be silently ignored if it is set to a non-numeric value.
1364 Clone an existing Git repository for use with
1366 This step currently requires
1370 .Dl $ git clone --bare https://github.com/openbsd/src.git
1372 Alternatively, for quick and dirty local testing of
1374 a new Git repository could be created and populated with files,
1375 e.g. from a temporary CVS checkout located at
1378 .Dl $ got init /var/git/src.git
1379 .Dl $ got import -r /var/git/src.git -I CVS -I obj /tmp/src
1381 Check out a work tree from the Git repository to /usr/src:
1383 .Dl $ got checkout /var/git/src.git /usr/src
1385 View local changes in a work tree directory:
1388 .Dl $ got diff | less
1390 Interactively revert selected local changes in a work tree directory:
1392 .Dl $ got revert -p -R\ .
1394 In a work tree or a git repository directory, list all branch references:
1398 In a work tree or a git repository directory, create a new branch called
1399 .Dq unified-buffer-cache
1400 which is forked off the
1404 .Dl $ got branch unified-buffer-cache master
1406 Switch an existing work tree to the branch
1407 .Dq unified-buffer-cache .
1408 Local changes in the work tree will be preserved and merged if necessary:
1410 .Dl $ got update -b unified-buffer-cache
1412 Create a new commit from local changes in a work tree directory.
1413 This new commit will become the head commit of the work tree's current branch:
1417 In a work tree or a git repository directory, view changes committed in
1418 the 3 most recent commits to the work tree's branch, or the branch resolved
1419 via the repository's HEAD reference, respectively:
1421 .Dl $ got log -p -l 3 -f
1423 Add new files and remove obsolete files in a work tree directory:
1425 .Dl $ got add sys/uvm/uvm_ubc.c
1426 .Dl $ got remove sys/uvm/uvm_vnode.c
1428 Create a new commit from local changes in a work tree directory
1429 with a pre-defined log message.
1431 .Dl $ got commit -m 'unify the buffer cache'
1433 Update any work tree checked out from the
1434 .Dq unified-buffer-cache
1435 branch to the latest commit on this branch:
1439 Roll file content on the unified-buffer-cache branch back by one commit,
1440 and then fetch the rolled-back change into the work tree as a local change
1441 to be amended and perhaps committed again:
1443 .Dl $ got backout unified-buffer-cache
1444 .Dl $ got commit -m 'roll back previous'
1445 .Dl $ # now back out the previous backout :-)
1446 .Dl $ got backout unified-buffer-cache
1448 Fetch new upstream commits into the local repository's master branch.
1449 This step currently requires
1452 .Dl $ cd /var/git/src.git
1453 .Dl $ git fetch origin master:master
1456 .Dq unified-buffer-cache
1457 branch on top of the new head commit of the
1461 .Dl $ got update -b master
1462 .Dl $ got rebase unified-buffer-cache
1464 Create a patch from all changes on the unified-buffer-cache branch.
1465 The patch can be mailed out for review and applied to
1469 .Dl $ got diff master unified-buffer-cache > /tmp/ubc.diff
1471 Edit the entire commit history of the
1472 .Dq unified-buffer-cache
1475 .Dl $ got update -b unified-buffer-cache
1476 .Dl $ got update -c master
1479 Additional steps are necessary if local changes need to be pushed back
1480 to the remote repository, which currently requires
1484 Before working against existing branches in a repository cloned with
1485 .Dq git clone --bare ,
1488 must be configured to map all references in the remote repository
1491 namespace of the local repository.
1492 This can achieved by setting Git's
1493 .Pa remote.origin.fetch
1494 configuration variable to the value
1495 .Dq +refs/heads/*:refs/remotes/origin/*
1500 .Dl $ cd /var/git/repo
1501 .Dl $ git config remote.origin.fetch '+refs/heads/*:refs/remotes/origin/*'
1503 Alternatively, the following
1505 configuration item can be added manually to the Git repository's
1509 .Dl [remote "origin"]
1511 .Dl fetch = +refs/heads/*:refs/remotes/origin/*
1513 This configuration leaves the local repository's
1515 namespace free for use by local branches checked out with
1517 and, if needed, created with
1522 namespace can be updated with incoming changes from the remote
1526 .Dl $ cd /var/git/repo
1529 Before outgoing changes on the local
1531 branch can be pushed to the remote repository, the local
1533 branch must be rebased onto the
1537 .Dl $ got update -b origin/master
1538 .Dl $ got rebase master
1540 Changes on the local
1542 branch can then be pushed to the remote
1546 .Dl $ cd /var/git/repo
1547 .Dl $ git push origin master
1549 In order to merge changes committed to the
1550 .Dq unified-buffer-cache
1551 branch back into the
1554 .Dq unified-buffer-cache
1555 branch must first be rebased onto the
1559 .Dl $ got update -b master
1560 .Dl $ got rebase unified-buffer-cache
1563 .Dq unified-buffer-cache
1564 branch can now be made visible on the
1568 Because the rebase operation switched the work tree to the
1569 .Dq unified-buffer-cache
1570 branch, the work tree must be switched back to the
1573 .Dq unified-buffer-cache
1574 branch can be integrated into
1577 .Dl $ got update -b master
1578 .Dl $ got integrate unified-buffer-cache
1582 .Xr git-repository 5 ,
1585 .An Stefan Sperling Aq Mt stsp@openbsd.org
1586 .An Martin Pieuchot Aq Mt mpi@openbsd.org
1587 .An Joshua Stein Aq Mt jcs@openbsd.org
1590 is a work-in-progress and many commands remain to be implemented.
1591 At present, the user has to fall back on
1593 to perform many tasks, in particular tasks related to repository
1594 administration and tasks which require a network connection.
