Blob


1 .\"
2 .\" Copyright (c) 2017 Martin Pieuchot
3 .\" Copyright (c) 2018, 2019 Stefan Sperling
4 .\"
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.
8 .\"
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.
16 .\"
17 .Dd $Mdocdate$
18 .Dt GOT 1
19 .Os
20 .Sh NAME
21 .Nm got
22 .Nd version control system
23 .Sh SYNOPSIS
24 .Nm
25 .Ar command
26 .Op Fl h
27 .Op Ar arg ...
28 .Sh DESCRIPTION
29 .Nm
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 .
34 .Pp
35 .Nm
36 is a
37 .Dq distributed
38 version control system because every copy of a repository is writeable.
39 Modifications made to files can be synchronized between repositories
40 at any time.
41 .Pp
42 Files managed by
43 .Nm
44 must be checked out from the repository for modification.
45 Checked out files are stored in a
46 .Em work tree
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
49 .Xr got-worktree 5 .
50 .Pp
51 .Nm
52 provides global and command-specific options.
53 Global options must preceed the command name, and are as follows:
54 .Bl -tag -width tenletters
55 .It Fl h
56 Display usage information.
57 .El
58 .Pp
59 The commands for
60 .Nm
61 are as follows:
62 .Bl -tag -width checkout
63 .It Cm checkout [ Fl c Ar commit ] [ Fl p Ar path-prefix ] repository-path [ work-tree-path ]
64 Copy files from a repository into a new work tree.
65 If the
66 .Ar work tree path
67 is not specified, either use the last component of
68 .Ar repository path ,
69 or if a
70 .Ar path prefix
71 was specified use the last component of
72 .Ar path prefix .
73 .Pp
74 The options for
75 .Cm got checkout
76 are as follows:
77 .Bl -tag -width Ds
78 .It Fl c Ar commit
79 Check out files from the specified
80 .Ar commit .
81 If this option is not specified, a commit resolved via the repository's HEAD
82 reference will be used.
83 .It Fl p Ar path-prefix
84 Restrict the work tree to a subset of the repository's tree hierarchy.
85 Only files beneath the specified
86 .Ar path-prefix
87 will be checked out.
88 .El
89 .It Cm update [ Fl c Ar commit ] [ Ar path ]
90 Update an existing work tree to another commit on the current branch.
91 By default, the latest commit on the current branch is assumed.
92 Show the status of each affected file, using the following status codes:
93 .Bl -column YXZ description
94 .It U Ta file was updated and contained no local changes
95 .It G Ta file was updated and local changes were merged cleanly
96 .It C Ta file was updated and conflicts occurred during merge
97 .It D Ta file was deleted
98 .It A Ta new file was added
99 .It ~ Ta versioned file is obstructed by a non-regular file
100 .It ! Ta a missing versioned file was restored
101 .El
102 .Pp
103 If a
104 .Ar path
105 is specified, restrict the update operation to files at or within this path.
106 The path is required to exist in the update operation's target commit.
107 Files in the work tree outside this path will remain unchanged and will
108 retain their previously recorded base commit.
109 Some
110 .Nm
111 commands may refuse to run while the work tree contains files from
112 multiple base commits.
113 The base commit of such a work tree can be made consistent by running
114 another update operation across the entire work tree.
115 .Pp
116 The options for
117 .Cm got update
118 are as follows:
119 .Bl -tag -width Ds
120 .It Fl c Ar commit
121 Update the work tree to the specified
122 .Ar commit .
123 The expected argument is a SHA1 hash which corresponds to a commit object.
124 .El
125 .It Cm status [ Ar path ]
126 Show the current modification status of files in a work tree,
127 using the following status codes:
128 .Bl -column YXZ description
129 .It M Ta modified file
130 .It A Ta file scheduled for addition in next commit
131 .It D Ta file scheduled for deletion in next commit
132 .It C Ta modified or added file which contains merge conflicts
133 .It ! Ta versioned file was expected on disk but is missing
134 .It ~ Ta versioned file is obstructed by a non-regular file
135 .It ? Ta unversioned item not tracked by
136 .Nm
137 .El
138 .Pp
139 If a
140 .Ar path
141 is specified, only show modifications within this path.
142 .It Cm log [ Fl c Ar commit ] [ Fl C Ar number ] [ Fl f ] [ Fl l Ar N ] [ Fl p ] [ Fl r Ar repository-path ] [ path ]
143 Display history of a repository.
144 If a
145 .Ar path
146 is specified, show only commits which modified this path.
147 .Pp
148 The options for
149 .Cm got log
150 are as follows:
151 .Bl -tag -width Ds
152 .It Fl c Ar commit
153 Start traversing history at the specified
154 .Ar commit .
155 The expected argument is the name of a branch or a SHA1 hash which corresponds
156 to a commit object.
157 .It Fl C Ar number
158 Set the number of context lines shown in diffs with
159 .Fl p .
160 By default, 3 lines of context are shown.
161 .It Fl f
162 Restrict history traversal to the first parent of each commit.
163 This shows the linear history of the current branch only.
164 Merge commits which affected the current branch will be shown but
165 individual commits which originated on other branches will be omitted.
166 .It Fl l Ar N
167 Limit history traversal to a given number of commits.
168 .It Fl p
169 Display the patch of modifications made in each commit.
170 .It Fl r Ar repository-path
171 Use the repository at the specified path.
172 If not specified, assume the repository is located at or above the current
173 working directory.
174 If this directory is a
175 .Nm
176 work tree, use the repository path associated with this work tree.
177 .El
178 .It Cm diff [ Fl C Ar number ] [ Fl r Ar repository-path ] [ Ar object1 Ar object2 | Ar path ]
179 When invoked within a work tree with less than two arguments, display
180 uncommitted changes in the work tree.
181 If a
182 .Ar path
183 is specified, only show changes within this path.
184 .Pp
185 If two arguments are provided, treat each argument as a SHA1 hash which
186 corresponds to an object in the repository, and display differences
187 between these objects.
188 Both objects must be of the same type (blobs, trees, or commits).
189 .Pp
190 The options for
191 .Cm got diff
192 are as follows:
193 .Bl -tag -width Ds
194 .It Fl C Ar number
195 Set the number of context lines shown in the diff.
196 By default, 3 lines of context are shown.
197 .It Fl r Ar repository-path
198 Use the repository at the specified path.
199 If not specified, assume the repository is located at or above the current
200 working directory.
201 If this directory is a
202 .Nm
203 work tree, use the repository path associated with this work tree.
204 .El
205 .It Cm blame [ Fl c Ar commit ] [ Fl r Ar repository-path ] Ar path
206 Display line-by-line history of a file at the specified path.
207 .Pp
208 The options for
209 .Cm got blame
210 are as follows:
211 .Bl -tag -width Ds
212 .It Fl c Ar commit
213 Start traversing history at the specified
214 .Ar commit .
215 The expected argument is the name of a branch or a SHA1 hash which corresponds
216 to a commit object.
217 .It Fl r Ar repository-path
218 Use the repository at the specified path.
219 If not specified, assume the repository is located at or above the current
220 working directory.
221 If this directory is a
222 .Nm
223 work tree, use the repository path associated with this work tree.
224 .El
225 .It Cm tree [ Fl c Ar commit ] [ Fl r Ar repository-path ] [ Fl i ] [ Fl R] [ Ar path ]
226 Display a listing of files and directories at the specified
227 directory path in the repository.
228 Entries shown in this listing may carry one of the following trailing
229 annotations:
230 .Bl -column YXZ description
231 .It / Ta entry is a directory
232 .It * Ta entry is an executable file
233 .El
234 .Pp
235 If no
236 .Ar path
237 is specified, list the repository path corresponding to the current
238 directory of the work tree, or the root directory of the repository
239 if there is no work tree.
240 .Pp
241 The options for
242 .Cm got tree
243 are as follows:
244 .Bl -tag -width Ds
245 .It Fl c Ar commit
246 List files and directories as they appear in the specified
247 .Ar commit .
248 The expected argument is the name of a branch or a SHA1 hash which corresponds
249 to a commit object.
250 .It Fl r Ar repository-path
251 Use the repository at the specified path.
252 If not specified, assume the repository is located at or above the current
253 working directory.
254 If this directory is a
255 .Nm
256 work tree, use the repository path associated with this work tree.
257 .It Fl i
258 Show object IDs of files (blob objects) and directories (tree objects).
259 .It Fl R
260 Recurse into sub-directories in the repository.
261 .El
262 .It Cm ref [ Fl r Ar repository-path ] [ Fl l ] [ Fl d Ar name ] [ Ar name Ar object ]
263 Manage references in a repository.
264 .Pp
265 If no options are passed, expect two arguments and attempt to create,
266 or update, the reference with the given
267 .Ar name ,
268 and make it point at the given
269 .Ar object .
270 The object argument is a SHA1 hash which corresponds to an existing
271 object in the repository.
272 .Pp
273 The options for
274 .Cm got ref
275 are as follows:
276 .Bl -tag -width Ds
277 .It Fl r Ar repository-path
278 Use the repository at the specified path.
279 If not specified, assume the repository is located at or above the current
280 working directory.
281 If this directory is a
282 .Nm
283 work tree, use the repository path associated with this work tree.
284 .It Fl l
285 List all existing references in the repository.
286 .It Fl d Ar name
287 Delete the reference with the specified name from the repository.
288 .El
289 .It Cm add Ar file-path
290 Schedule an unversioned file in a work tree for addition to the
291 repository in the next commit.
292 .It Cm rm Ar file-path
293 Remove a versioned file from a work tree and schedule it for deletion
294 from the repository in the next commit.
295 .Pp
296 The options for
297 .Cm got rm
298 are as follows:
299 .Bl -tag -width Ds
300 .It Fl f
301 Perform the operation even if the file contains uncommitted modifications.
302 .El
303 .It Cm revert Ar file-path
304 Revert any uncommited changes in the file at the specified path.
305 File contents will be overwritten with those contained in the
306 work tree's base commit. There is no way to bring discarded
307 changes back after
308 .Cm got revert !
309 .Pp
310 If the file was added with
311 .Cm got add
312 it will become an unversioned file again.
313 If the file was deleted with
314 .Cm got rm
315 it will be restored.
316 .El
317 .Sh EXIT STATUS
318 .Ex -std got
319 .Sh EXAMPLES
320 Check out a work tree of
321 .Ox
322 kernel sources from a Git repository at /var/repo/openbsd-src to ~/sys:
323 .Pp
324 .Dl $ got checkout -p sys /var/repo/openbsd-src ~/sys
325 .Sh SEE ALSO
326 .Xr git-repository 5
327 .Xr got-worktree 5
328 .Sh AUTHORS
329 .An Stefan Sperling Aq Mt stsp@openbsd.org
330 .An Martin Pieuchot Aq Mt mpi@openbsd.org