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.
102 instead of creating the default branch
104 Use of this option is required if the
106 branch already exists.
108 Use the specified log message when creating the new commit.
113 opens a temporary file in an editor where a log message can be written.
114 .It Fl r Ar repository-path
115 Use the repository at the specified path.
116 If not specified, assume the repository is located at or above the current
119 Ignore files or directories with a name which matches the specified
121 This option may be specified multiple times to build a list of ignore patterns.
124 follows the globbing rules documented in
130 .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
131 Copy files from a repository into a new work tree.
134 is not specified, either use the last component of
135 .Ar repository path ,
138 was specified use the last component of
146 Check out files from a commit on the specified
148 If this option is not specified, a branch resolved via the repository's HEAD
149 reference will be used.
151 Check out files from the specified
153 on the selected branch.
154 The expected argument is a commit ID SHA1 hash or an existing reference
155 or tag name which will be resolved to a commit ID.
156 An abbreviated hash argument will be expanded to a full SHA1 hash
157 automatically, provided the abbreviation is unique.
158 If this option is not specified, the most recent commit on the selected
160 .It Fl p Ar path-prefix
161 Restrict the work tree to a subset of the repository's tree hierarchy.
162 Only files beneath the specified
169 .It Cm update Oo Fl b Ar branch Oc Oo Fl c Ar commit Oc Op Ar path ...
170 Update an existing work tree to a different commit.
171 Show the status of each affected file, using the following status codes:
172 .Bl -column YXZ description
173 .It U Ta file was updated and contained no local changes
174 .It G Ta file was updated and local changes were merged cleanly
175 .It C Ta file was updated and conflicts occurred during merge
176 .It D Ta file was deleted
177 .It A Ta new file was added
178 .It \(a~ Ta versioned file is obstructed by a non-regular file
179 .It ! Ta a missing versioned file was restored
184 is specified, update the entire work tree.
185 Otherwise, restrict the update operation to files at or within the
187 Each path is required to exist in the update operation's target commit.
188 Files in the work tree outside specified paths will remain unchanged and
189 will retain their previously recorded base commit.
192 commands may refuse to run while the work tree contains files from
193 multiple base commits.
194 The base commit of such a work tree can be made consistent by running
196 across the entire work tree.
199 is incompatible with the
204 cannot update paths with staged changes.
205 If changes have been staged with
207 these changes must first be committed with
217 Switch the work tree's branch reference to the specified
219 before updating the work tree.
220 This option requires that all paths in the work tree are updated.
222 Update the work tree to the specified
224 The expected argument is a commit ID SHA1 hash or an existing reference
225 or tag name which will be resolved to a commit ID.
226 An abbreviated hash argument will be expanded to a full SHA1 hash
227 automatically, provided the abbreviation is unique.
228 If this option is not specified, the most recent commit on the work tree's
234 .It Cm status Op Ar path ...
235 Show the current modification status of files in a work tree,
236 using the following status codes:
237 .Bl -column YXZ description
238 .It M Ta modified file
239 .It A Ta file scheduled for addition in next commit
240 .It D Ta file scheduled for deletion in next commit
241 .It C Ta modified or added file which contains merge conflicts
242 .It ! Ta versioned file was expected on disk but is missing
243 .It \(a~ Ta versioned file is obstructed by a non-regular file
244 .It ? Ta unversioned item not tracked by
250 is specified, show modifications in the entire work tree.
251 Otherwise, show modifications at or within the specified paths.
253 If changes have been staged with
255 staged changes are shown in the second output column, using the following
257 .Bl -column YXZ description
258 .It M Ta file modification is staged
259 .It A Ta file addition is staged
260 .It D Ta file deletion is staged
263 Changes created on top of staged changes are indicated in the first column:
264 .Bl -column YXZ description
265 .It MM Ta file was modified after earlier changes have been staged
266 .It MA Ta file was modified after having been staged for addition
269 For compatibility with
274 files in each traversed directory and will not display unversioned files
277 ignore patterns contained in
283 only supports a single ignore pattern per line.
287 .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 r Ar repository-path Oc Op Ar path
288 Display history of a repository.
291 is specified, show only commits which modified this path.
298 Start traversing history at the specified
300 The expected argument is a commit ID SHA1 hash or an existing reference
301 or tag name which will be resolved to a commit ID.
302 An abbreviated hash argument will be expanded to a full SHA1 hash
303 automatically, provided the abbreviation is unique.
304 If this option is not specified, default to the work tree's current branch
305 if invoked in a work tree, or to the repository's HEAD reference.
307 Set the number of context lines shown in diffs with
309 By default, 3 lines of context are shown.
311 Restrict history traversal to the first parent of each commit.
312 This shows the linear history of the current branch only.
313 Merge commits which affected the current branch will be shown but
314 individual commits which originated on other branches will be omitted.
316 Limit history traversal to a given number of commits.
317 If this option is not specified, a default limit value of zero is used,
318 which is treated as an unbounded limit.
320 .Ev GOT_LOG_DEFAULT_LIMIT
321 environment variable may be set to change this default value.
323 Display the patch of modifications made in each commit.
324 .It Fl r Ar repository-path
325 Use the repository at the specified path.
326 If not specified, assume the repository is located at or above the current
328 If this directory is a
330 work tree, use the repository path associated with this work tree.
332 .It Cm diff Oo Fl C Ar number Oc Oo Fl r Ar repository-path Oc Oo Fl s Oc Op Ar object1 Ar object2 | Ar path
333 When invoked within a work tree with less than two arguments, display
334 uncommitted changes in the work tree.
337 is specified, only show changes within this path.
339 If two arguments are provided, treat each argument as a reference, a tag
340 name, or an object ID SHA1 hash, and display differences between the
341 corresponding objects.
342 Both objects must be of the same type (blobs, trees, or commits).
343 An abbreviated hash argument will be expanded to a full SHA1 hash
344 automatically, provided the abbreviation is unique.
351 Set the number of context lines shown in the diff.
352 By default, 3 lines of context are shown.
353 .It Fl r Ar repository-path
354 Use the repository at the specified path.
355 If not specified, assume the repository is located at or above the current
357 If this directory is a
359 work tree, use the repository path associated with this work tree.
361 Show changes staged with
363 instead of showing local changes.
364 This option is only valid when
366 is invoked in a work tree.
371 .It Cm blame Oo Fl c Ar commit Oc Oo Fl r Ar repository-path Oc Ar path
372 Display line-by-line history of a file at the specified path.
379 Start traversing history at the specified
381 The expected argument is a commit ID SHA1 hash or an existing reference
382 or tag name which will be resolved to a commit ID.
383 An abbreviated hash argument will be expanded to a full SHA1 hash
384 automatically, provided the abbreviation is unique.
385 .It Fl r Ar repository-path
386 Use the repository at the specified path.
387 If not specified, assume the repository is located at or above the current
389 If this directory is a
391 work tree, use the repository path associated with this work tree.
396 .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
397 Display a listing of files and directories at the specified
398 directory path in the repository.
399 Entries shown in this listing may carry one of the following trailing
401 .Bl -column YXZ description
402 .It @ Ta entry is a symbolic link
403 .It / Ta entry is a directory
404 .It * Ta entry is an executable file
409 is specified, list the repository path corresponding to the current
410 directory of the work tree, or the root directory of the repository
411 if there is no work tree.
418 List files and directories as they appear in the specified
420 The expected argument is a commit ID SHA1 hash or an existing reference
421 or tag name which will be resolved to a commit ID.
422 An abbreviated hash argument will be expanded to a full SHA1 hash
423 automatically, provided the abbreviation is unique.
424 .It Fl r Ar repository-path
425 Use the repository at the specified path.
426 If not specified, assume the repository is located at or above the current
428 If this directory is a
430 work tree, use the repository path associated with this work tree.
432 Show object IDs of files (blob objects) and directories (tree objects).
434 Recurse into sub-directories in the repository.
439 .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
440 Manage references in a repository.
442 If no options are passed, expect two arguments and attempt to create,
443 or update, the reference with the given
445 and make it point at the given
447 The target may be an object ID SHA1 hash or an existing reference which
448 will be resolved to an object ID.
449 An abbreviated hash argument will be expanded to a full SHA1 hash
450 automatically, provided the abbreviation is unique.
456 .It Fl r Ar repository-path
457 Use the repository at the specified path.
458 If not specified, assume the repository is located at or above the current
460 If this directory is a
462 work tree, use the repository path associated with this work tree.
464 List all existing references in the repository.
466 Delete the reference with the specified name from the repository.
468 Create a symbolic reference pointing at the specified
470 which must be an existing reference.
471 Care should be taken not to create loops between references when
474 .It Cm branch Oo Fl r Ar repository-path Oc Oo Fl l Oc Oo Fl d Ar name Oc Op Ar name Op Ar base-branch
475 Manage branches in a repository.
477 Branches are managed via references which live in the
482 command operates on references in this namespace only.
484 If no options are passed, expect one or two arguments and attempt to create
485 a branch with the given
487 and make it point at the given
491 is specified, default to the work tree's current branch if invoked in a
492 work tree, or to the repository's HEAD reference.
498 .It Fl r Ar repository-path
499 Use the repository at the specified path.
500 If not specified, assume the repository is located at or above the current
502 If this directory is a
504 work tree, use the repository path associated with this work tree.
506 List all existing branches in the repository.
507 If invoked in a work tree, the work tree's current branch is shown
508 with one the following annotations:
509 .Bl -column YXZ description
510 .It * Ta work tree's base commit matches the branch tip
511 .It \(a~ Ta work tree's base commit is out-of-date
514 Delete the branch with the specified name from the repository.
515 Only the branch reference is deleted.
516 Any commit, tree, and blob objects belonging to the branch
517 remain in the repository and may be removed separately with
518 Git's garbage collector.
523 .It Cm add Ar file-path ...
524 Schedule unversioned files in a work tree for addition to the
525 repository in the next commit.
526 .It Cm remove Ar file-path ...
527 Remove versioned files from a work tree and schedule them for deletion
528 from the repository in the next commit.
535 Perform the operation even if a file contains uncommitted modifications.
540 .It Cm revert Oo Fl p Oc Oo Fl F Ar response-script Oc Oo Fl R Oc Ar path ...
541 Revert any uncommitted changes in files at the specified paths.
542 File contents will be overwritten with those contained in the
543 work tree's base commit.
544 There is no way to bring discarded changes back after
547 If a file was added with
549 it will become an unversioned file again.
550 If a file was deleted with
559 Instead of reverting all changes in files, interactively select or reject
560 changes to revert based on
566 (quit reverting this file) responses.
567 If a file is in modified status, individual patches derived from the
568 modified file content can be reverted.
569 Files in added or deleted status may only be reverted in their entirety.
570 .It Fl F Ar response-script
578 responses line-by-line from the specified
580 file instead of prompting interactively.
582 Permit recursion into directories.
583 If this option is not specified,
585 will refuse to run if a specified
592 .It Cm commit Oo Fl m Ar message Oc Op Ar path ...
593 Create a new commit in the repository from changes in a work tree
594 and use this commit as the new base commit for the work tree.
597 is specified, commit all changes in the work tree.
598 Otherwise, commit changes at or within the specified paths.
600 If changes have been explicitly staged for commit with
602 only commit staged changes and reject any specified paths which
603 have not been staged.
605 Show the status of each affected file, using the following status codes:
606 .Bl -column YXZ description
607 .It M Ta modified file
608 .It D Ta file was deleted
609 .It A Ta new file was added
612 Files which are not part of the new commit will retain their previously
613 recorded base commit.
616 commands may refuse to run while the work tree contains files from
617 multiple base commits.
618 The base commit of such a work tree can be made consistent by running
620 across the entire work tree.
626 environment variable to be set.
633 Use the specified log message when creating the new commit.
638 opens a temporary file in an editor where a log message can be written.
642 will refuse to run if certain preconditions are not met.
643 If the work tree's current branch is not in the
645 reference namespace, new commits may not be created on this branch.
646 Local changes may only be committed if they are based on file content
647 found in the most recent commit on the work tree's branch.
648 If a path is found to be out of date,
650 must be used first in order to merge local changes with changes made
655 .It Cm cherrypick Ar commit
656 Merge changes from a single
661 must be on a different branch than the work tree's base commit.
662 The expected argument is a reference or a commit ID SHA1 hash.
663 An abbreviated hash argument will be expanded to a full SHA1 hash
664 automatically, provided the abbreviation is unique.
666 Show the status of each affected file, using the following status codes:
667 .Bl -column YXZ description
668 .It G Ta file was merged
669 .It C Ta file was merged and conflicts occurred during merge
670 .It ! Ta changes destined for a missing file were not merged
671 .It D Ta file was deleted
672 .It d Ta file's deletion was obstructed by local modifications
673 .It A Ta new file was added
674 .It \(a~ Ta changes destined for a non-regular file were not merged
677 The merged changes will appear as local changes in the work tree, which
680 amended manually or with further
685 or discarded again with
689 will refuse to run if certain preconditions are not met.
690 If the work tree contains multiple base commits it must first be updated
691 to a single base commit with
693 If the work tree already contains files with merge conflicts, these
694 conflicts must be resolved first.
698 .It Cm backout Ar commit
699 Reverse-merge changes from a single
704 must be on the same branch as the work tree's base commit.
705 The expected argument is a reference or a commit ID SHA1 hash.
706 An abbreviated hash argument will be expanded to a full SHA1 hash
707 automatically, provided the abbreviation is unique.
709 Show the status of each affected file, using the following status codes:
710 .Bl -column YXZ description
711 .It G Ta file was merged
712 .It C Ta file was merged and conflicts occurred during merge
713 .It ! Ta changes destined for a missing file were not merged
714 .It D Ta file was deleted
715 .It d Ta file's deletion was obstructed by local modifications
716 .It A Ta new file was added
717 .It \(a~ Ta changes destined for a non-regular file were not merged
720 The reverse-merged changes will appear as local changes in the work tree,
721 which may be viewed with
723 amended manually or with further
728 or discarded again with
732 will refuse to run if certain preconditions are not met.
733 If the work tree contains multiple base commits it must first be updated
734 to a single base commit with
736 If the work tree already contains files with merge conflicts, these
737 conflicts must be resolved first.
741 .It Cm rebase Oo Fl a Oc Oo Fl c Oc Op Ar branch
742 Rebase commits on the specified
744 onto the tip of the current branch of the work tree.
747 must share common ancestry with the work tree's current branch.
748 Rebasing begins with the first descendant commit of the youngest
749 common ancestor commit shared by the specified
751 and the work tree's current branch, and stops once the tip commit
756 Rebased commits are accumulated on a temporary branch which the work tree
757 will remain switched to throughout the entire rebase operation.
758 Commits on this branch represent the same changes with the same log
759 messages as their counterparts on the original
761 but with different commit IDs.
762 Once rebasing has completed successfully, the temporary branch becomes
763 the new version of the specified
765 and the work tree is automatically switched to it.
767 While rebasing commits, show the status of each affected file,
768 using the following status codes:
769 .Bl -column YXZ description
770 .It G Ta file was merged
771 .It C Ta file was merged and conflicts occurred during merge
772 .It ! Ta changes destined for a missing file were not merged
773 .It D Ta file was deleted
774 .It d Ta file's deletion was obstructed by local modifications
775 .It A Ta new file was added
776 .It \(a~ Ta changes destined for a non-regular file were not merged
779 If merge conflicts occur the rebase operation is interrupted and may
780 be continued once conflicts have been resolved.
781 Alternatively, the rebase operation may be aborted which will leave
783 unmodified and the work tree switched back to its original branch.
785 If a merge conflict is resolved in a way which renders the merged
786 change into a no-op change, the corresponding commit will be elided
787 when the rebase operation continues.
790 will refuse to run if certain preconditions are not met.
791 If the work tree contains multiple base commits it must first be updated
792 to a single base commit with
794 If changes have been staged with
796 these changes must first be committed with
800 If the work tree contains local changes, these changes must first be
807 contains changes to files outside of the work tree's path prefix,
808 the work tree cannot be used to rebase this branch.
814 commands will refuse to run while a rebase operation is in progress.
815 Other commands which manipulate the work tree may be used for
816 conflict resolution purposes.
823 Abort an interrupted rebase operation.
824 If this option is used, no other command-line arguments are allowed.
826 Continue an interrupted rebase operation.
827 If this option is used, no other command-line arguments are allowed.
832 .It Cm histedit Oo Fl a Oc Oo Fl c Oc Op Fl F Ar histedit-script
833 Edit commit history between the work tree's current base commit and
834 the tip commit of the work tree's current branch.
836 Editing of commit history is controlled via a
838 which can be edited interactively or passed on the command line.
839 The format of the histedit script is line-based.
840 Each line in the script begins with a command name, followed by
841 whitespace and an argument.
842 For most commands, the expected argument is a commit ID SHA1 hash.
843 Any remaining text on the line is ignored.
844 Lines which begin with the
846 character are ignored entirely.
848 The available commands are as follows:
849 .Bl -column YXZ pick-commit
850 .It pick Ar commit Ta Use the specified commit as it is.
851 .It edit Ar commit Ta Use the specified commit but once changes have been
852 merged into the work tree interrupt the histedit operation for amending.
853 .It fold Ar commit Ta Combine the specified commit with the next commit
854 listed further below that will be used.
855 .It drop Ar commit Ta Remove this commit from the edited history.
856 .It mesg Ar log-message Ta Use the specified single-line log message for
857 the commit on the previous line.
858 If the log message argument is left empty, open an editor where a new
859 log message can be written.
862 Every commit in the history being edited must be mentioned in the script.
863 Lines may be re-ordered to change the order of commits in the edited history.
865 Edited commits are accumulated on a temporary branch which the work tree
866 will remain switched to throughout the entire histedit operation.
867 Once history editing has completed successfully, the temporary branch becomes
868 the new version of the work tree's branch and the work tree is automatically
871 While merging commits, show the status of each affected file,
872 using the following status codes:
873 .Bl -column YXZ description
874 .It G Ta file was merged
875 .It C Ta file was merged and conflicts occurred during merge
876 .It ! Ta changes destined for a missing file were not merged
877 .It D Ta file was deleted
878 .It d Ta file's deletion was obstructed by local modifications
879 .It A Ta new file was added
880 .It \(a~ Ta changes destined for a non-regular file were not merged
883 If merge conflicts occur the histedit operation is interrupted and may
884 be continued once conflicts have been resolved.
885 Alternatively, the histedit operation may be aborted which will leave
886 the work tree switched back to its original branch.
888 If a merge conflict is resolved in a way which renders the merged
889 change into a no-op change, the corresponding commit will be elided
890 when the histedit operation continues.
893 will refuse to run if certain preconditions are not met.
894 If the work tree's current branch is not in the
896 reference namespace, the history of the branch may not be edited.
897 If the work tree contains multiple base commits it must first be updated
898 to a single base commit with
900 If changes have been staged with
902 these changes must first be committed with
906 If the work tree contains local changes, these changes must first be
911 If the edited history contains changes to files outside of the work tree's
912 path prefix, the work tree cannot be used to edit the history of this branch.
916 command will refuse to run while a histedit operation is in progress.
917 Other commands which manipulate the work tree may be used, and the
919 command may be used to commit arbitrary changes to the temporary branch
920 while the histedit operation is interrupted.
927 Abort an interrupted histedit operation.
928 If this option is used, no other command-line arguments are allowed.
930 Continue an interrupted histedit operation.
931 If this option is used, no other command-line arguments are allowed.
936 .It Cm stage Oo Fl l Oc Oo Fl p Oc Oo Fl F Ar response-script Oc Op Ar path ...
937 Stage local changes for inclusion in the next commit.
940 is specified, stage all changes in the work tree.
941 Otherwise, stage changes at or within the specified paths.
942 Paths may be staged if they are added, modified, or deleted according to
945 Show the status of each affected file, using the following status codes:
946 .Bl -column YXZ description
947 .It A Ta file addition has been staged
948 .It M Ta file modification has been staged
949 .It D Ta file deletion has been staged
952 Staged file contents are saved in newly created blob objects in the repository.
953 These blobs will be referred to by tree objects once staged changes have been
956 Staged changes affect the behaviour of
961 While paths with staged changes exist, the
963 command will refuse to commit any paths which do not have staged changes.
964 Local changes created on top of staged changes can only be committed if
965 the path is staged again, or if the staged changes are committed first.
968 command will show both local changes and staged changes.
971 command is able to display local changes relative to staged changes,
972 and to display staged changes relative to the repository.
975 command cannot revert staged changes but may be used to revert
976 local changes created on top of staged changes.
983 Instead of staging new changes, list paths which are already staged,
984 along with the IDs of staged blob objects and stage status codes.
985 If paths were provided in the command line show the staged paths
986 among the specified paths.
987 Otherwise, show all staged paths.
989 Instead of staging the entire content of a changed file, interactively
990 select or reject changes for staging based on
996 (quit staging this file) responses.
997 If a file is in modified status, individual patches derived from the
998 modified file content can be staged.
999 Files in added or deleted status may only be staged or rejected in
1001 .It Fl F Ar response-script
1009 responses line-by-line from the specified
1011 file instead of prompting interactively.
1015 will refuse to run if certain preconditions are not met.
1016 If a file contains merge conflicts, these conflicts must be resolved first.
1017 If a file is found to be out of date relative to the head commit on the
1018 work tree's current branch, the file must be updated with
1020 before it can be staged (however, this does not prevent the file from
1021 becoming out-of-date at some point after having been staged).
1028 commands will refuse to run while staged changes exist.
1029 If staged changes cannot be committed because a staged path
1030 is out of date, the path must be unstaged with
1032 before it can be updated with
1034 and may then be staged again if necessary.
1038 .It Cm unstage Oo Fl p Oc Oo Fl F Ar response-script Oc Op Ar path ...
1039 Merge staged changes back into the work tree and put affected paths
1040 back into non-staged status.
1043 is specified, unstage all staged changes across the entire work tree.
1044 Otherwise, unstage changes at or within the specified paths.
1046 Show the status of each affected file, using the following status codes:
1047 .Bl -column YXZ description
1048 .It G Ta file was unstaged
1049 .It C Ta file was unstaged and conflicts occurred during merge
1050 .It ! Ta changes destined for a missing file were not merged
1051 .It D Ta file was staged as deleted and still is deleted
1052 .It d Ta file's deletion was obstructed by local modifications
1053 .It \(a~ Ta changes destined for a non-regular file were not merged
1061 Instead of unstaging the entire content of a changed file, interactively
1062 select or reject changes for unstaging based on
1066 (keep change staged), and
1068 (quit unstaging this file) responses.
1069 If a file is staged in modified status, individual patches derived from the
1070 staged file content can be unstaged.
1071 Files staged in added or deleted status may only be unstaged in their entirety.
1072 .It Fl F Ar response-script
1080 responses line-by-line from the specified
1082 file instead of prompting interactively.
1089 .Bl -tag -width GOT_AUTHOR
1091 The author's name and email address for
1096 .An Flan Hacker Aq Mt flan_hacker@openbsd.org .
1099 may fail to parse commits without an email address in author data,
1103 environment variables with a missing email address.
1104 .It Ev VISUAL , EDITOR
1105 The editor spawned by
1107 .It Ev GOT_LOG_DEFAULT_LIMIT
1108 The default limit on the number of commits traversed by
1110 If set to zero, the limit is unbounded.
1111 This variable will be silently ignored if it is set to a non-numeric value.
1116 Clone an existing Git repository for use with
1118 This step currently requires
1122 .Dl $ git clone --bare https://github.com/openbsd/src.git
1124 Alternatively, for quick and dirty local testing of
1126 a new Git repository could be created and populated with files,
1127 e.g. from a temporary CVS checkout located at
1130 .Dl $ got init /var/git/src.git
1131 .Dl $ got import -r /var/git/src.git -I CVS -I obj /tmp/src
1133 Check out a work tree from the Git repository to /usr/src:
1135 .Dl $ got checkout /var/git/src.git /usr/src
1137 View local changes in a work tree directory:
1140 .Dl $ got diff | less
1142 Interactively revert selected local changes in a work tree directory:
1144 .Dl $ got revert -p -R\ .
1146 In a work tree or a git repository directory, list all branch references:
1150 In a work tree or a git repository directory, create a new branch called
1151 .Dq unified-buffer-cache
1152 which is forked off the
1156 .Dl $ got branch unified-buffer-cache master
1158 Switch an existing work tree to the branch
1159 .Dq unified-buffer-cache .
1160 Local changes in the work tree will be preserved and merged if necessary:
1162 .Dl $ got update -b unified-buffer-cache
1164 Create a new commit from local changes in a work tree directory.
1165 This new commit will become the head commit of the work tree's current branch:
1169 In a work tree or a git repository directory, view changes committed in
1170 the 3 most recent commits to the work tree's branch, or the branch resolved
1171 via the repository's HEAD reference, respectively:
1173 .Dl $ got log -p -l 3 -f
1175 Add new files and remove obsolete files in a work tree directory:
1177 .Dl $ got add sys/uvm/uvm_ubc.c
1178 .Dl $ got remove sys/uvm/uvm_vnode.c
1180 Create a new commit from local changes in a work tree directory
1181 with a pre-defined log message.
1183 .Dl $ got commit -m 'unify the buffer cache'
1185 Update any work tree checked out from the
1186 .Dq unified-buffer-cache
1187 branch to the latest commit on this branch:
1191 Roll file content on the unified-buffer-cache branch back by one commit,
1192 and then fetch the rolled-back change into the work tree as a local change
1193 to be amended and perhaps committed again:
1195 .Dl $ got backout unified-buffer-cache
1196 .Dl $ got commit -m 'roll back previous'
1197 .Dl $ # now back out the previous backout :-)
1198 .Dl $ got backout unified-buffer-cache
1200 Fetch new upstream commits into the local repository's master branch.
1201 This step currently requires
1204 .Dl $ cd /var/git/src.git
1205 .Dl $ git fetch origin master:master
1208 .Dq unified-buffer-cache
1209 branch on top of the new head commit of the
1213 .Dl $ got update -b master
1214 .Dl $ got rebase unified-buffer-cache
1216 Create a patch from all changes on the unified-buffer-cache branch.
1217 The patch can be mailed out for review and applied to
1221 .Dl $ got diff master unified-buffer-cache > /tmp/ubc.diff
1223 Edit the entire commit history of the
1224 .Dq unified-buffer-cache
1227 .Dl $ got update -b unified-buffer-cache
1228 .Dl $ got update -c master
1231 Additional steps are necessary if local changes need to be pushed back
1232 to the remote repository, which currently requires
1236 Before working against existing branches in a repository cloned with
1237 .Dq git clone --bare ,
1240 must be configured to map all references in the remote repository
1243 namespace of the local repository.
1244 This can achieved by setting Git's
1245 .Pa remote.origin.fetch
1246 configuration variable to the value
1247 .Dq +refs/heads/*:refs/remotes/origin/*
1252 .Dl $ cd /var/git/repo
1253 .Dl $ git config remote.origin.fetch '+refs/heads/*:refs/remotes/origin/*'
1255 Alternatively, the following
1257 configuration item can be added manually to the Git repository's
1261 .Dl [remote "origin"]
1263 .Dl fetch = +refs/heads/*:refs/remotes/origin/*
1265 This configuration leaves the local repository's
1267 namespace free for use by local branches checked out with
1269 and, if needed, created with
1274 namespace can be updated with incoming changes from the remote
1278 .Dl $ cd /var/git/repo
1281 Before outgoing changes on the local
1283 branch can be pushed to the remote repository, the local
1285 branch must be rebased onto the
1289 .Dl $ got update -b origin/master
1290 .Dl $ got rebase master
1292 Changes on the local
1294 branch can then be pushed to the remote
1298 .Dl $ cd /var/git/repo
1299 .Dl $ git push origin master
1302 .Xr git-repository 5 ,
1305 .An Stefan Sperling Aq Mt stsp@openbsd.org
1306 .An Martin Pieuchot Aq Mt mpi@openbsd.org
1307 .An Joshua Stein Aq Mt jcs@openbsd.org
1310 is a work-in-progress and many commands remain to be implemented.
1311 At present, the user has to fall back on
1313 to perform many tasks, in particular tasks related to repository
1314 administration and tasks which require a network connection.
