]>
Commit | Line | Data |
---|---|---|
3397f9df EW |
1 | git-svn(1) |
2 | ========== | |
3 | ||
4 | NAME | |
5 | ---- | |
2de9b711 | 6 | git-svn - Bidirectional operation between a Subversion repository and Git |
3397f9df EW |
7 | |
8 | SYNOPSIS | |
9 | -------- | |
7791a1d9 | 10 | [verse] |
b1889c36 | 11 | 'git svn' <command> [options] [arguments] |
3397f9df EW |
12 | |
13 | DESCRIPTION | |
14 | ----------- | |
2de9b711 TA |
15 | 'git svn' is a simple conduit for changesets between Subversion and Git. |
16 | It provides a bidirectional flow of changes between a Subversion and a Git | |
1168d402 | 17 | repository. |
3397f9df | 18 | |
647ac702 | 19 | 'git svn' can track a standard Subversion repository, |
ab81a364 MB |
20 | following the common "trunk/branches/tags" layout, with the --stdlayout option. |
21 | It can also follow branches and tags in any layout with the -T/-t/-b options | |
22 | (see options to 'init' below, and also the 'clone' command). | |
3397f9df | 23 | |
2de9b711 | 24 | Once tracking a Subversion repository (with any of the above methods), the Git |
8cb070a4 | 25 | repository can be updated from Subversion by the 'fetch' command and |
2de9b711 | 26 | Subversion updated from Git by the 'dcommit' command. |
3397f9df EW |
27 | |
28 | COMMANDS | |
29 | -------- | |
0ea4d4c9 JF |
30 | |
31 | 'init':: | |
2de9b711 | 32 | Initializes an empty Git repository with additional |
647ac702 | 33 | metadata directories for 'git svn'. The Subversion URL |
a836a0e1 EW |
34 | may be specified as a command-line argument, or as full |
35 | URL arguments to -T/-t/-b. Optionally, the target | |
36 | directory to operate on can be specified as a second | |
37 | argument. Normally this command initializes the current | |
38 | directory. | |
3397f9df | 39 | |
cc1793e2 KW |
40 | -T<trunk_subdir>;; |
41 | --trunk=<trunk_subdir>;; | |
42 | -t<tags_subdir>;; | |
43 | --tags=<tags_subdir>;; | |
44 | -b<branches_subdir>;; | |
45 | --branches=<branches_subdir>;; | |
8f728fb9 | 46 | -s;; |
47 | --stdlayout;; | |
a836a0e1 EW |
48 | These are optional command-line options for init. Each of |
49 | these flags can point to a relative repository path | |
ab81a364 MB |
50 | (--tags=project/tags) or a full url |
51 | (--tags=https://foo.org/project/tags). | |
52 | You can specify more than one --tags and/or --branches options, in case | |
53 | your Subversion repository places tags or branches under multiple paths. | |
54 | The option --stdlayout is | |
8f728fb9 | 55 | a shorthand way of setting trunk,tags,branches as the relative paths, |
56 | which is the Subversion default. If any of the other options are given | |
57 | as well, they take precedence. | |
cc1793e2 | 58 | --no-metadata;; |
0dfaf0a4 | 59 | Set the 'noMetadata' option in the [svn-remote] config. |
c9be27f3 EW |
60 | This option is not recommended, please read the 'svn.noMetadata' |
61 | section of this manpage before using this option. | |
cc1793e2 | 62 | --use-svm-props;; |
0dfaf0a4 | 63 | Set the 'useSvmProps' option in the [svn-remote] config. |
cc1793e2 | 64 | --use-svnsync-props;; |
0dfaf0a4 | 65 | Set the 'useSvnsyncProps' option in the [svn-remote] config. |
cc1793e2 | 66 | --rewrite-root=<URL>;; |
0dfaf0a4 | 67 | Set the 'rewriteRoot' option in the [svn-remote] config. |
3e18ce1a JS |
68 | --rewrite-uuid=<UUID>;; |
69 | Set the 'rewriteUUID' option in the [svn-remote] config. | |
3b0d2405 | 70 | --username=<user>;; |
a0d7fe3f SV |
71 | For transports that SVN handles authentication for (http, |
72 | https, and plain svn), specify the username. For other | |
f745acb0 TA |
73 | transports (e.g. svn+ssh://), you must include the username in |
74 | the URL, e.g. svn+ssh://foo@svn.bar.com/project | |
cc1793e2 | 75 | --prefix=<prefix>;; |
a836a0e1 EW |
76 | This allows one to specify a prefix which is prepended |
77 | to the names of remotes if trunk/branches/tags are | |
78 | specified. The prefix does not automatically include a | |
79 | trailing slash, so be sure you include one in the | |
0d351e9c GP |
80 | argument if that is what you want. If --branches/-b is |
81 | specified, the prefix must include a trailing slash. | |
7091a2d0 JH |
82 | Setting a prefix (with a trailing slash) is strongly |
83 | encouraged in any case, as your SVN-tracking refs will | |
84 | then be located at "refs/remotes/$prefix/*", which is | |
85 | compatible with Git's own remote-tracking ref layout | |
86 | (refs/remotes/$remote/*). Setting a prefix is also useful | |
87 | if you wish to track multiple projects that share a common | |
88 | repository. | |
fe191fca | 89 | By default, the prefix is set to 'origin/'. |
f849bb6b | 90 | + |
fe191fca JH |
91 | NOTE: Before Git v2.0, the default prefix was "" (no prefix). This |
92 | meant that SVN-tracking refs were put at "refs/remotes/*", which is | |
93 | incompatible with how Git's own remote-tracking refs are organized. | |
7bbc458b KM |
94 | If you still want the old default, you can get it by passing |
95 | `--prefix ""` on the command line (`--prefix=""` may not work if | |
96 | your Perl's Getopt::Long is < v2.37). | |
f849bb6b | 97 | |
88ec2054 BJ |
98 | --ignore-paths=<regex>;; |
99 | When passed to 'init' or 'clone' this regular expression will | |
100 | be preserved as a config key. See 'fetch' for a description | |
101 | of '--ignore-paths'. | |
a7b10230 PW |
102 | --include-paths=<regex>;; |
103 | When passed to 'init' or 'clone' this regular expression will | |
104 | be preserved as a config key. See 'fetch' for a description | |
105 | of '--include-paths'. | |
6b48829d EW |
106 | --no-minimize-url;; |
107 | When tracking multiple directories (using --stdlayout, | |
108 | --branches, or --tags options), git svn will attempt to connect | |
109 | to the root (or highest allowed level) of the Subversion | |
110 | repository. This default allows better tracking of history if | |
111 | entire projects are moved within a repository, but may cause | |
112 | issues on repositories where read access restrictions are in | |
113 | place. Passing '--no-minimize-url' will allow git svn to | |
114 | accept URLs as-is without attempting to connect to a higher | |
115 | level directory. This option is off by default when only | |
116 | one URL/branch is tracked (it would do little good). | |
81c5a0e6 | 117 | |
a836a0e1 | 118 | 'fetch':: |
a836a0e1 EW |
119 | Fetch unfetched revisions from the Subversion remote we are |
120 | tracking. The name of the [svn-remote "..."] section in the | |
6fe7a30a KK |
121 | $GIT_DIR/config file may be specified as an optional |
122 | command-line argument. | |
945b9c14 KK |
123 | + |
124 | This automatically updates the rev_map if needed (see | |
125 | '$GIT_DIR/svn/\*\*/.rev_map.*' in the FILES section below for details). | |
b705ba43 | 126 | |
e82f0d73 | 127 | --localtime;; |
0ffa154b | 128 | Store Git commit times in the local time zone instead of UTC. This |
647ac702 | 129 | makes 'git log' (even without --date=local) show the same times |
0ffa154b | 130 | that `svn log` would in the local time zone. |
6c32a7a9 | 131 | + |
e82f0d73 PH |
132 | This doesn't interfere with interoperating with the Subversion |
133 | repository you cloned from, but if you wish for your local Git | |
134 | repository to be able to interoperate with someone else's local Git | |
135 | repository, either don't use this option or you should both use it in | |
0ffa154b | 136 | the same local time zone. |
e82f0d73 | 137 | |
61f36a79 TS |
138 | --parent;; |
139 | Fetch only from the SVN parent of the current HEAD. | |
140 | ||
6076b843 | 141 | --ignore-paths=<regex>;; |
0d8bee71 | 142 | This allows one to specify a Perl regular expression that will |
6076b843 | 143 | cause skipping of all matching paths from checkout from SVN. |
0d8bee71 BJ |
144 | The '--ignore-paths' option should match for every 'fetch' |
145 | (including automatic fetches due to 'clone', 'dcommit', | |
146 | 'rebase', etc) on a given repository. | |
6c32a7a9 YD |
147 | + |
148 | [verse] | |
0d8bee71 | 149 | config key: svn-remote.<name>.ignore-paths |
6c32a7a9 | 150 | + |
06ab60c0 JSJ |
151 | If the ignore-paths configuration key is set, and the command-line |
152 | option is also given, both regular expressions will be used. | |
6c32a7a9 | 153 | + |
0d8bee71 | 154 | Examples: |
6c32a7a9 YD |
155 | + |
156 | -- | |
157 | Skip "doc*" directory for every fetch;; | |
158 | + | |
159 | ------------------------------------------------------------------------ | |
160 | --ignore-paths="^doc" | |
161 | ------------------------------------------------------------------------ | |
0d8bee71 | 162 | |
6c32a7a9 YD |
163 | Skip "branches" and "tags" of first level directories;; |
164 | + | |
165 | ------------------------------------------------------------------------ | |
166 | --ignore-paths="^[^/]+/(?:branches|tags)" | |
167 | ------------------------------------------------------------------------ | |
168 | -- | |
6076b843 | 169 | |
a7b10230 PW |
170 | --include-paths=<regex>;; |
171 | This allows one to specify a Perl regular expression that will | |
172 | cause the inclusion of only matching paths from checkout from SVN. | |
173 | The '--include-paths' option should match for every 'fetch' | |
174 | (including automatic fetches due to 'clone', 'dcommit', | |
175 | 'rebase', etc) on a given repository. '--ignore-paths' takes | |
176 | precedence over '--include-paths'. | |
177 | ||
bc22b277 | 178 | --log-window-size=<n>;; |
3c123fb8 SB |
179 | Fetch <n> log entries per request when scanning Subversion history. |
180 | The default is 100. For very large Subversion repositories, larger | |
181 | values may be needed for 'clone'/'fetch' to complete in reasonable | |
182 | time. But overly large values may lead to higher memory usage and | |
183 | request timeouts. | |
bc22b277 | 184 | |
a81ed0b6 EW |
185 | 'clone':: |
186 | Runs 'init' and 'fetch'. It will automatically create a | |
187 | directory based on the basename of the URL passed to it; | |
188 | or if a second argument is passed; it will create a directory | |
189 | and work within that. It accepts all arguments that the | |
190 | 'init' and 'fetch' commands accept; with the exception of | |
0da3e1d2 YD |
191 | '--fetch-all' and '--parent'. After a repository is cloned, |
192 | the 'fetch' command will be able to update revisions without | |
193 | affecting the working tree; and the 'rebase' command will be | |
194 | able to update the working tree with the latest changes. | |
a81ed0b6 | 195 | |
40a1530c RC |
196 | --preserve-empty-dirs;; |
197 | Create a placeholder file in the local Git repository for each | |
198 | empty directory fetched from Subversion. This includes directories | |
199 | that become empty by removing all entries in the Subversion | |
200 | repository (but not the directory itself). The placeholder files | |
201 | are also tracked and removed when no longer necessary. | |
202 | ||
203 | --placeholder-filename=<filename>;; | |
204 | Set the name of placeholder files created by --preserve-empty-dirs. | |
205 | Default: ".gitignore" | |
206 | ||
a81ed0b6 EW |
207 | 'rebase':: |
208 | This fetches revisions from the SVN parent of the current HEAD | |
209 | and rebases the current (uncommitted to SVN) work against it. | |
6c32a7a9 | 210 | + |
647ac702 YD |
211 | This works similarly to `svn update` or 'git pull' except that |
212 | it preserves linear history with 'git rebase' instead of | |
213 | 'git merge' for ease of dcommitting with 'git svn'. | |
6c32a7a9 | 214 | + |
647ac702 | 215 | This accepts all options that 'git svn fetch' and 'git rebase' |
483bc4f0 | 216 | accept. However, '--fetch-all' only fetches from the current |
112f6385 | 217 | [svn-remote], and not all [svn-remote] definitions. |
6c32a7a9 | 218 | + |
647ac702 | 219 | Like 'git rebase'; this requires that the working tree be clean |
112f6385 | 220 | and have no uncommitted changes. |
945b9c14 KK |
221 | + |
222 | This automatically updates the rev_map if needed (see | |
223 | '$GIT_DIR/svn/\*\*/.rev_map.*' in the FILES section below for details). | |
cc1793e2 | 224 | |
dee41f3e EW |
225 | -l;; |
226 | --local;; | |
647ac702 | 227 | Do not fetch remotely; only run 'git rebase' against the |
dee41f3e | 228 | last fetched commit from the upstream SVN. |
a81ed0b6 | 229 | |
b22d4497 | 230 | 'dcommit':: |
2b26b65f | 231 | Commit each diff from the current branch directly to the SVN |
b22d4497 | 232 | repository, and then rebase or reset (depending on whether or |
2eff1425 | 233 | not there is a diff between SVN and head). This will create |
2de9b711 | 234 | a revision in SVN for each commit in Git. |
2b26b65f | 235 | + |
2de9b711 | 236 | When an optional Git branch name (or a Git commit object name) |
2b26b65f JS |
237 | is specified as an argument, the subcommand works on the specified |
238 | branch, not on the current branch. | |
239 | + | |
240 | Use of 'dcommit' is preferred to 'set-tree' (below). | |
171af110 KW |
241 | + |
242 | --no-rebase;; | |
243 | After committing, do not rebase or reset. | |
ba24e745 EW |
244 | --commit-url <URL>;; |
245 | Commit to this SVN URL (the full path). This is intended to | |
647ac702 | 246 | allow existing 'git svn' repositories created with one transport |
ba24e745 EW |
247 | method (e.g. `svn://` or `http://` for anonymous read) to be |
248 | reused if a user is later given access to an alternate transport | |
249 | method (e.g. `svn+ssh://` or `https://`) for commit. | |
6c32a7a9 YD |
250 | + |
251 | [verse] | |
0df84059 | 252 | config key: svn-remote.<name>.commiturl |
0df84059 | 253 | config key: svn.commiturl (overwrites all svn-remote.<name>.commiturl options) |
6c32a7a9 | 254 | + |
f947ae4b SK |
255 | Note that the SVN URL of the commiturl config key includes the SVN branch. |
256 | If you rather want to set the commit URL for an entire SVN repository use | |
257 | svn-remote.<name>.pushurl instead. | |
258 | + | |
6c32a7a9 YD |
259 | Using this option for any other purpose (don't ask) is very strongly |
260 | discouraged. | |
b22d4497 | 261 | |
ccc2fcf5 MG |
262 | --mergeinfo=<mergeinfo>;; |
263 | Add the given merge information during the dcommit | |
264 | (e.g. `--mergeinfo="/branches/foo:1-10"`). All svn server versions can | |
265 | store this information (as a property), and svn clients starting from | |
98c4ab32 BJ |
266 | version 1.5 can make use of it. To specify merge information from multiple |
267 | branches, use a single space character between the branches | |
268 | (`--mergeinfo="/branches/foo:1-10 /branches/bar:3,5-6,8"`) | |
1e5814f3 BJ |
269 | + |
270 | [verse] | |
271 | config key: svn.pushmergeinfo | |
272 | + | |
273 | This option will cause git-svn to attempt to automatically populate the | |
274 | svn:mergeinfo property in the SVN repository when possible. Currently, this can | |
275 | only be done when dcommitting non-fast-forward merges where all parents but the | |
276 | first have already been pushed into SVN. | |
ccc2fcf5 | 277 | |
afd7f1eb FH |
278 | --interactive;; |
279 | Ask the user to confirm that a patch set should actually be sent to SVN. | |
280 | For each patch, one may answer "yes" (accept this patch), "no" (discard this | |
281 | patch), "all" (accept all patches), or "quit". | |
5a8a19e9 JK |
282 | + |
283 | 'git svn dcommit' returns immediately if answer is "no" or "quit", without | |
284 | committing anything to SVN. | |
afd7f1eb | 285 | |
5de70efb FR |
286 | 'branch':: |
287 | Create a branch in the SVN repository. | |
288 | ||
289 | -m;; | |
290 | --message;; | |
291 | Allows to specify the commit message. | |
292 | ||
293 | -t;; | |
294 | --tag;; | |
295 | Create a tag by using the tags_subdir instead of the branches_subdir | |
296 | specified during git svn init. | |
297 | ||
7d82b4af JN |
298 | -d<path>;; |
299 | --destination=<path>;; | |
300 | ||
ab81a364 MB |
301 | If more than one --branches (or --tags) option was given to the 'init' |
302 | or 'clone' command, you must provide the location of the branch (or | |
7d82b4af JN |
303 | tag) you wish to create in the SVN repository. <path> specifies which |
304 | path to use to create the branch or tag and should match the pattern | |
305 | on the left-hand side of one of the configured branches or tags | |
306 | refspecs. You can see these refspecs with the commands | |
ab81a364 MB |
307 | + |
308 | git config --get-all svn-remote.<name>.branches | |
309 | git config --get-all svn-remote.<name>.tags | |
310 | + | |
311 | where <name> is the name of the SVN repository as specified by the -R option to | |
312 | 'init' (or "svn" by default). | |
313 | ||
a65f3c20 IM |
314 | --username;; |
315 | Specify the SVN username to perform the commit as. This option overrides | |
cb82dbf8 | 316 | the 'username' configuration property. |
a65f3c20 IM |
317 | |
318 | --commit-url;; | |
319 | Use the specified URL to connect to the destination Subversion | |
320 | repository. This is useful in cases where the source SVN | |
321 | repository is read-only. This option overrides configuration | |
322 | property 'commiturl'. | |
323 | + | |
324 | git config --get-all svn-remote.<name>.commiturl | |
325 | + | |
326 | ||
f4f4c7fc TS |
327 | --parents;; |
328 | Create parent folders. This parameter is equivalent to the parameter | |
329 | --parents on svn cp commands and is useful for non-standard repository | |
330 | layouts. | |
331 | ||
5de70efb FR |
332 | 'tag':: |
333 | Create a tag in the SVN repository. This is a shorthand for | |
334 | 'branch -t'. | |
335 | ||
e8f5d908 EW |
336 | 'log':: |
337 | This should make it easy to look up svn log messages when svn | |
338 | users refer to -r/--revision numbers. | |
112f6385 SV |
339 | + |
340 | The following features from `svn log' are supported: | |
341 | + | |
342 | -- | |
6c32a7a9 YD |
343 | -r <n>[:<n>];; |
344 | --revision=<n>[:<n>];; | |
112f6385 SV |
345 | is supported, non-numeric args are not: |
346 | HEAD, NEXT, BASE, PREV, etc ... | |
6c32a7a9 YD |
347 | -v;; |
348 | --verbose;; | |
112f6385 SV |
349 | it's not completely compatible with the --verbose |
350 | output in svn log, but reasonably close. | |
351 | --limit=<n>;; | |
352 | is NOT the same as --max-count, doesn't count | |
353 | merged/excluded commits | |
354 | --incremental;; | |
355 | supported | |
356 | -- | |
357 | + | |
358 | New features: | |
359 | + | |
360 | -- | |
361 | --show-commit;; | |
2de9b711 | 362 | shows the Git commit sha1, as well |
112f6385 SV |
363 | --oneline;; |
364 | our version of --pretty=oneline | |
365 | -- | |
366 | + | |
a50a5c8f MV |
367 | NOTE: SVN itself only stores times in UTC and nothing else. The regular svn |
368 | client converts the UTC time to the local time (or based on the TZ= | |
369 | environment). This command has the same behaviour. | |
370 | + | |
647ac702 | 371 | Any other arguments are passed directly to 'git log' |
e8f5d908 | 372 | |
6fb5375e | 373 | 'blame':: |
3c123fb8 SB |
374 | Show what revision and author last modified each line of a file. The |
375 | output of this mode is format-compatible with the output of | |
376 | `svn blame' by default. Like the SVN blame command, | |
377 | local uncommitted changes in the working tree are ignored; | |
378 | the version of the file in the HEAD revision is annotated. Unknown | |
379 | arguments are passed directly to 'git blame'. | |
6fb5375e | 380 | + |
4be40381 | 381 | --git-format;; |
647ac702 | 382 | Produce output in the same format as 'git blame', but with |
2de9b711 | 383 | SVN revision numbers instead of Git commit hashes. In this mode, |
4be40381 SG |
384 | changes that haven't been committed to SVN (including local |
385 | working-copy edits) are shown as revision 0. | |
6fb5375e | 386 | |
26e60160 AR |
387 | 'find-rev':: |
388 | When given an SVN revision number of the form 'rN', returns the | |
2de9b711 | 389 | corresponding Git commit hash (this can optionally be followed by a |
b3cb7e45 AR |
390 | tree-ish to specify which branch should be searched). When given a |
391 | tree-ish, returns the corresponding SVN revision number. | |
2934a484 | 392 | + |
a831a3fd | 393 | -B;; |
2934a484 JK |
394 | --before;; |
395 | Don't require an exact match if given an SVN revision, instead find | |
396 | the commit corresponding to the state of the SVN repository (on the | |
397 | current branch) at the specified revision. | |
398 | + | |
a831a3fd | 399 | -A;; |
2934a484 JK |
400 | --after;; |
401 | Don't require an exact match if given an SVN revision; if there is | |
402 | not an exact match return the closest match searching forward in the | |
403 | history. | |
26e60160 | 404 | |
3289e86e | 405 | 'set-tree':: |
e8f5d908 | 406 | You should consider using 'dcommit' instead of this command. |
3397f9df EW |
407 | Commit specified commit or tree objects to SVN. This relies on |
408 | your imported fetch data being up-to-date. This makes | |
409 | absolutely no attempts to do patching when committing to SVN, it | |
410 | simply overwrites files with those specified in the tree or | |
411 | commit. All merging is assumed to have taken place | |
647ac702 | 412 | independently of 'git svn' functions. |
3397f9df | 413 | |
da060c67 | 414 | 'create-ignore':: |
da060c67 GH |
415 | Recursively finds the svn:ignore property on directories and |
416 | creates matching .gitignore files. The resulting files are staged to | |
69239728 | 417 | be committed, but are not committed. Use -r/--revision to refer to a |
1168d402 | 418 | specific revision. |
da060c67 | 419 | |
0ea4d4c9 | 420 | 'show-ignore':: |
8f22562c EW |
421 | Recursively finds and lists the svn:ignore property on |
422 | directories. The output is suitable for appending to | |
423 | the $GIT_DIR/info/exclude file. | |
424 | ||
6111b934 | 425 | 'mkdirs':: |
2de9b711 | 426 | Attempts to recreate empty directories that core Git cannot track |
6111b934 EW |
427 | based on information in $GIT_DIR/svn/<refname>/unhandled.log files. |
428 | Empty directories are automatically recreated when using | |
429 | "git svn clone" and "git svn rebase", so "mkdirs" is intended | |
430 | for use after commands like "git checkout" or "git reset". | |
55f9d7a7 MH |
431 | (See the svn-remote.<name>.automkdirs config file option for |
432 | more information.) | |
6111b934 | 433 | |
e8f5d908 EW |
434 | 'commit-diff':: |
435 | Commits the diff of two tree-ish arguments from the | |
647ac702 | 436 | command-line. This command does not rely on being inside an `git svn |
483bc4f0 | 437 | init`-ed repository. This command takes three arguments, (a) the |
e8f5d908 EW |
438 | original tree to diff against, (b) the new tree result, (c) the |
439 | URL of the target Subversion repository. The final argument | |
647ac702 YD |
440 | (URL) may be omitted if you are working from a 'git svn'-aware |
441 | repository (that has been `init`-ed with 'git svn'). | |
45bf473a | 442 | The -r<revision> option is required for this. |
e8f5d908 | 443 | |
e6fefa92 DK |
444 | 'info':: |
445 | Shows information about a file or directory similar to what | |
446 | `svn info' provides. Does not currently support a -r/--revision | |
8b014d71 DK |
447 | argument. Use the --url option to output only the value of the |
448 | 'URL:' field. | |
e6fefa92 | 449 | |
69239728 GH |
450 | 'proplist':: |
451 | Lists the properties stored in the Subversion repository about a | |
452 | given file or directory. Use -r/--revision to refer to a specific | |
453 | Subversion revision. | |
454 | ||
455 | 'propget':: | |
456 | Gets the Subversion property given as the first argument, for a | |
457 | file. A specific revision can be specified with -r/--revision. | |
458 | ||
459 | 'show-externals':: | |
460 | Shows the Subversion externals. Use -r/--revision to specify a | |
461 | specific revision. | |
462 | ||
2da9ee08 | 463 | 'gc':: |
e618c396 KK |
464 | Compress $GIT_DIR/svn/<refname>/unhandled.log files and remove |
465 | $GIT_DIR/svn/<refname>/index files. | |
2da9ee08 | 466 | |
195643f2 BJ |
467 | 'reset':: |
468 | Undoes the effects of 'fetch' back to the specified revision. | |
469 | This allows you to re-'fetch' an SVN revision. Normally the | |
470 | contents of an SVN revision should never change and 'reset' | |
471 | should not be necessary. However, if SVN permissions change, | |
472 | or if you alter your --ignore-paths option, a 'fetch' may fail | |
473 | with "not found in commit" (file not previously visible) or | |
474 | "checksum mismatch" (missed a modification). If the problem | |
475 | file cannot be ignored forever (with --ignore-paths) the only | |
476 | way to repair the repo is to use 'reset'. | |
6c32a7a9 | 477 | + |
945b9c14 KK |
478 | Only the rev_map and refs/remotes/git-svn are changed (see |
479 | '$GIT_DIR/svn/\*\*/.rev_map.*' in the FILES section below for details). | |
480 | Follow 'reset' with a 'fetch' and then 'git reset' or 'git rebase' to | |
481 | move local branches onto the new tree. | |
195643f2 | 482 | |
6c32a7a9 YD |
483 | -r <n>;; |
484 | --revision=<n>;; | |
195643f2 BJ |
485 | Specify the most recent revision to keep. All later revisions |
486 | are discarded. | |
6c32a7a9 YD |
487 | -p;; |
488 | --parent;; | |
195643f2 BJ |
489 | Discard the specified revision as well, keeping the nearest |
490 | parent instead. | |
491 | Example:;; | |
492 | Assume you have local changes in "master", but you need to refetch "r2". | |
6c32a7a9 | 493 | + |
195643f2 BJ |
494 | ------------ |
495 | r1---r2---r3 remotes/git-svn | |
496 | \ | |
497 | A---B master | |
498 | ------------ | |
6c32a7a9 | 499 | + |
195643f2 BJ |
500 | Fix the ignore-paths or SVN permissions problem that caused "r2" to |
501 | be incomplete in the first place. Then: | |
6c32a7a9 | 502 | + |
195643f2 BJ |
503 | [verse] |
504 | git svn reset -r2 -p | |
505 | git svn fetch | |
6c32a7a9 | 506 | + |
195643f2 BJ |
507 | ------------ |
508 | r1---r2'--r3' remotes/git-svn | |
509 | \ | |
510 | r2---r3---A---B master | |
511 | ------------ | |
6c32a7a9 | 512 | + |
647ac702 YD |
513 | Then fixup "master" with 'git rebase'. |
514 | Do NOT use 'git merge' or your history will not be compatible with a | |
195643f2 | 515 | future 'dcommit'! |
6c32a7a9 | 516 | + |
195643f2 BJ |
517 | [verse] |
518 | git rebase --onto remotes/git-svn A^ master | |
6c32a7a9 | 519 | + |
195643f2 BJ |
520 | ------------ |
521 | r1---r2'--r3' remotes/git-svn | |
522 | \ | |
523 | A'--B' master | |
524 | ------------ | |
525 | ||
3397f9df EW |
526 | OPTIONS |
527 | ------- | |
0ea4d4c9 | 528 | |
0adda936 | 529 | --shared[=(false|true|umask|group|all|world|everybody)]:: |
e8f5d908 EW |
530 | --template=<template_directory>:: |
531 | Only used with the 'init' command. | |
647ac702 | 532 | These are passed directly to 'git init'. |
e8f5d908 | 533 | |
3b0d2405 MG |
534 | -r <arg>:: |
535 | --revision <arg>:: | |
6c32a7a9 YD |
536 | Used with the 'fetch' command. |
537 | + | |
a836a0e1 EW |
538 | This allows revision ranges for partial/cauterized history |
539 | to be supported. $NUMBER, $NUMBER1:$NUMBER2 (numeric ranges), | |
540 | $NUMBER:HEAD, and BASE:$NUMBER are all supported. | |
6c32a7a9 | 541 | + |
a836a0e1 EW |
542 | This can allow you to make partial mirrors when running fetch; |
543 | but is generally not recommended because history will be skipped | |
544 | and lost. | |
3397f9df EW |
545 | |
546 | -:: | |
547 | --stdin:: | |
6c32a7a9 YD |
548 | Only used with the 'set-tree' command. |
549 | + | |
0ea4d4c9 JF |
550 | Read a list of commits from stdin and commit them in reverse |
551 | order. Only the leading sha1 is read from each line, so | |
647ac702 | 552 | 'git rev-list --pretty=oneline' output can be used. |
3397f9df EW |
553 | |
554 | --rmdir:: | |
6c32a7a9 YD |
555 | Only used with the 'dcommit', 'set-tree' and 'commit-diff' commands. |
556 | + | |
0ea4d4c9 JF |
557 | Remove directories from the SVN tree if there are no files left |
558 | behind. SVN can version empty directories, and they are not | |
2de9b711 | 559 | removed by default if there are no files left in them. Git |
0ea4d4c9 | 560 | cannot version empty directories. Enabling this flag will make |
2de9b711 | 561 | the commit to SVN act like Git. |
6c32a7a9 YD |
562 | + |
563 | [verse] | |
e0d10e1c | 564 | config key: svn.rmdir |
20b1d700 | 565 | |
3397f9df EW |
566 | -e:: |
567 | --edit:: | |
6c32a7a9 YD |
568 | Only used with the 'dcommit', 'set-tree' and 'commit-diff' commands. |
569 | + | |
0ea4d4c9 JF |
570 | Edit the commit message before committing to SVN. This is off by |
571 | default for objects that are commits, and forced on when committing | |
572 | tree objects. | |
6c32a7a9 YD |
573 | + |
574 | [verse] | |
e0d10e1c | 575 | config key: svn.edit |
20b1d700 | 576 | |
72942938 EW |
577 | -l<num>:: |
578 | --find-copies-harder:: | |
6c32a7a9 YD |
579 | Only used with the 'dcommit', 'set-tree' and 'commit-diff' commands. |
580 | + | |
647ac702 | 581 | They are both passed directly to 'git diff-tree'; see |
5162e697 | 582 | linkgit:git-diff-tree[1] for more information. |
6c32a7a9 | 583 | + |
0ea4d4c9 | 584 | [verse] |
e0d10e1c TP |
585 | config key: svn.l |
586 | config key: svn.findcopiesharder | |
20b1d700 | 587 | |
81c5a0e6 EW |
588 | -A<filename>:: |
589 | --authors-file=<filename>:: | |
6c32a7a9 YD |
590 | Syntax is compatible with the file used by 'git cvsimport': |
591 | + | |
81c5a0e6 | 592 | ------------------------------------------------------------------------ |
0ea4d4c9 | 593 | loginname = Joe User <user@example.com> |
81c5a0e6 | 594 | ------------------------------------------------------------------------ |
6c32a7a9 | 595 | + |
647ac702 YD |
596 | If this option is specified and 'git svn' encounters an SVN |
597 | committer name that does not exist in the authors-file, 'git svn' | |
0ea4d4c9 | 598 | will abort operation. The user will then have to add the |
647ac702 | 599 | appropriate entry. Re-running the previous 'git svn' command |
0ea4d4c9 | 600 | after the authors-file is modified should continue operation. |
6c32a7a9 YD |
601 | + |
602 | [verse] | |
e0d10e1c | 603 | config key: svn.authorsfile |
e8f5d908 | 604 | |
36db1edd | 605 | --authors-prog=<filename>:: |
6c32a7a9 YD |
606 | If this option is specified, for each SVN committer name that |
607 | does not exist in the authors file, the given file is executed | |
608 | with the committer name as the first argument. The program is | |
609 | expected to return a single line of the form "Name <email>", | |
610 | which will be treated as if included in the authors file. | |
36db1edd | 611 | |
e8f5d908 EW |
612 | -q:: |
613 | --quiet:: | |
647ac702 | 614 | Make 'git svn' less verbose. Specify a second time to make it |
49750f30 | 615 | even less verbose. |
e8f5d908 | 616 | |
b22d4497 EW |
617 | -m:: |
618 | --merge:: | |
619 | -s<strategy>:: | |
620 | --strategy=<strategy>:: | |
b64e1f58 AL |
621 | -p:: |
622 | --preserve-merges:: | |
6c32a7a9 YD |
623 | These are only used with the 'dcommit' and 'rebase' commands. |
624 | + | |
647ac702 YD |
625 | Passed directly to 'git rebase' when using 'dcommit' if a |
626 | 'git reset' cannot be used (see 'dcommit'). | |
b22d4497 EW |
627 | |
628 | -n:: | |
629 | --dry-run:: | |
6c32a7a9 YD |
630 | This can be used with the 'dcommit', 'rebase', 'branch' and |
631 | 'tag' commands. | |
632 | + | |
2de9b711 | 633 | For 'dcommit', print out the series of Git arguments that would show |
b22d4497 | 634 | which diffs would be committed to SVN. |
6c32a7a9 | 635 | + |
7d45e146 SF |
636 | For 'rebase', display the local branch associated with the upstream svn |
637 | repository associated with the current branch and the URL of svn | |
638 | repository that will be fetched from. | |
6c32a7a9 | 639 | + |
5de70efb FR |
640 | For 'branch' and 'tag', display the urls that will be used for copying when |
641 | creating the branch or tag. | |
642 | ||
c88d18ff | 643 | --use-log-author:: |
2de9b711 | 644 | When retrieving svn commits into Git (as part of 'fetch', 'rebase', or |
7733b279 | 645 | 'dcommit' operations), look for the first `From:` or `Signed-off-by:` line |
c88d18ff VH |
646 | in the log message and use that as the author string. |
647 | --add-author-from:: | |
2de9b711 | 648 | When committing to svn from Git (as part of 'commit-diff', 'set-tree' or 'dcommit' |
c88d18ff | 649 | operations), if the existing log message doesn't already have a |
7733b279 | 650 | `From:` or `Signed-off-by:` line, append a `From:` line based on the |
2de9b711 | 651 | Git commit's author string. If you use this, then `--use-log-author` |
c88d18ff VH |
652 | will retrieve a valid author string for all commits. |
653 | ||
81c5a0e6 | 654 | |
448c81b4 EW |
655 | ADVANCED OPTIONS |
656 | ---------------- | |
0ea4d4c9 | 657 | |
448c81b4 EW |
658 | -i<GIT_SVN_ID>:: |
659 | --id <GIT_SVN_ID>:: | |
6c32a7a9 YD |
660 | This sets GIT_SVN_ID (instead of using the environment). This |
661 | allows the user to override the default refname to fetch from | |
662 | when tracking a single URL. The 'log' and 'dcommit' commands | |
663 | no longer require this switch as an argument. | |
0ea4d4c9 | 664 | |
9760adcc EW |
665 | -R<remote name>:: |
666 | --svn-remote <remote name>:: | |
667 | Specify the [svn-remote "<remote name>"] section to use, | |
a836a0e1 EW |
668 | this allows SVN multiple repositories to be tracked. |
669 | Default: "svn" | |
9760adcc | 670 | |
e8f5d908 | 671 | --follow-parent:: |
0d35bfe1 SL |
672 | This option is only relevant if we are tracking branches (using |
673 | one of the repository layout options --trunk, --tags, | |
674 | --branches, --stdlayout). For each tracked branch, try to find | |
675 | out where its revision was copied from, and set | |
2de9b711 | 676 | a suitable parent in the first Git commit for the branch. |
e8f5d908 | 677 | This is especially helpful when we're tracking a directory |
0d35bfe1 SL |
678 | that has been moved around within the repository. If this |
679 | feature is disabled, the branches created by 'git svn' will all | |
680 | be linear and not share any history, meaning that there will be | |
681 | no information on where branches were branched off or merged. | |
682 | However, following long/convoluted histories can take a long | |
683 | time, so disabling this feature may speed up the cloning | |
684 | process. This feature is enabled by default, use | |
0bed5eaa | 685 | --no-follow-parent to disable it. |
6c32a7a9 YD |
686 | + |
687 | [verse] | |
e0d10e1c | 688 | config key: svn.followparent |
e8f5d908 | 689 | |
a81ed0b6 EW |
690 | CONFIG FILE-ONLY OPTIONS |
691 | ------------------------ | |
a81ed0b6 | 692 | |
0dfaf0a4 EW |
693 | svn.noMetadata:: |
694 | svn-remote.<name>.noMetadata:: | |
6c32a7a9 YD |
695 | This gets rid of the 'git-svn-id:' lines at the end of every commit. |
696 | + | |
c9be27f3 EW |
697 | This option can only be used for one-shot imports as 'git svn' |
698 | will not be able to fetch again without metadata. Additionally, | |
945b9c14 | 699 | if you lose your '$GIT_DIR/svn/\*\*/.rev_map.*' files, 'git svn' will not |
c9be27f3 | 700 | be able to rebuild them. |
6c32a7a9 | 701 | + |
647ac702 | 702 | The 'git svn log' command will not work on repositories using |
112f6385 SV |
703 | this, either. Using this conflicts with the 'useSvmProps' |
704 | option for (hopefully) obvious reasons. | |
c9be27f3 EW |
705 | + |
706 | This option is NOT recommended as it makes it difficult to track down | |
707 | old references to SVN revision numbers in existing documentation, bug | |
2de9b711 | 708 | reports and archives. If you plan to eventually migrate from SVN to Git |
c9be27f3 EW |
709 | and are certain about dropping SVN history, consider |
710 | linkgit:git-filter-branch[1] instead. filter-branch also allows | |
469bfc96 | 711 | reformatting of metadata for ease-of-reading and rewriting authorship |
c9be27f3 | 712 | info for non-"svn.authorsFile" users. |
97ae0911 | 713 | |
0dfaf0a4 EW |
714 | svn.useSvmProps:: |
715 | svn-remote.<name>.useSvmProps:: | |
6c32a7a9 YD |
716 | This allows 'git svn' to re-map repository URLs and UUIDs from |
717 | mirrors created using SVN::Mirror (or svk) for metadata. | |
718 | + | |
112f6385 SV |
719 | If an SVN revision has a property, "svm:headrev", it is likely |
720 | that the revision was created by SVN::Mirror (also used by SVK). | |
721 | The property contains a repository UUID and a revision. We want | |
722 | to make it look like we are mirroring the original URL, so | |
723 | introduce a helper function that returns the original identity | |
724 | URL and UUID, and use it when generating metadata in commit | |
725 | messages. | |
97ae0911 | 726 | |
0dfaf0a4 EW |
727 | svn.useSvnsyncProps:: |
728 | svn-remote.<name>.useSvnsyncprops:: | |
a81ed0b6 EW |
729 | Similar to the useSvmProps option; this is for users |
730 | of the svnsync(1) command distributed with SVN 1.4.x and | |
731 | later. | |
732 | ||
0dfaf0a4 | 733 | svn-remote.<name>.rewriteRoot:: |
a81ed0b6 | 734 | This allows users to create repositories from alternate |
647ac702 | 735 | URLs. For example, an administrator could run 'git svn' on the |
a81ed0b6 EW |
736 | server locally (accessing via file://) but wish to distribute |
737 | the repository with a public http:// or svn:// URL in the | |
738 | metadata so users of it will see the public URL. | |
739 | ||
3e18ce1a JS |
740 | svn-remote.<name>.rewriteUUID:: |
741 | Similar to the useSvmProps option; this is for users who need | |
742 | to remap the UUID manually. This may be useful in situations | |
743 | where the original UUID is not available via either useSvmProps | |
744 | or useSvnsyncProps. | |
745 | ||
12a296bc AS |
746 | svn-remote.<name>.pushurl:: |
747 | ||
2de9b711 | 748 | Similar to Git's 'remote.<name>.pushurl', this key is designed |
12a296bc AS |
749 | to be used in cases where 'url' points to an SVN repository |
750 | via a read-only transport, to provide an alternate read/write | |
751 | transport. It is assumed that both keys point to the same | |
752 | repository. Unlike 'commiturl', 'pushurl' is a base path. If | |
753 | either 'commiturl' or 'pushurl' could be used, 'commiturl' | |
754 | takes precedence. | |
755 | ||
4c58a711 | 756 | svn.brokenSymlinkWorkaround:: |
6c32a7a9 YD |
757 | This disables potentially expensive checks to workaround |
758 | broken symlinks checked into SVN by broken clients. Set this | |
759 | option to "false" if you track a SVN repository with many | |
760 | empty blobs that are not symlinks. This option may be changed | |
761 | while 'git svn' is running and take effect on the next | |
762 | revision fetched. If unset, 'git svn' assumes this option to | |
763 | be "true". | |
3b2bbe9b | 764 | |
3713e222 DS |
765 | svn.pathnameencoding:: |
766 | This instructs git svn to recode pathnames to a given encoding. | |
767 | It can be used by windows users and by those who work in non-utf8 | |
768 | locales to avoid corrupted file names with non-ASCII characters. | |
769 | Valid encodings are the ones supported by Perl's Encode module. | |
770 | ||
55f9d7a7 MH |
771 | svn-remote.<name>.automkdirs:: |
772 | Normally, the "git svn clone" and "git svn rebase" commands | |
773 | attempt to recreate empty directories that are in the | |
774 | Subversion repository. If this option is set to "false", then | |
775 | empty directories will only be created if the "git svn mkdirs" | |
776 | command is run explicitly. If unset, 'git svn' assumes this | |
777 | option to be "true". | |
778 | ||
3e18ce1a | 779 | Since the noMetadata, rewriteRoot, rewriteUUID, useSvnsyncProps and useSvmProps |
647ac702 | 780 | options all affect the metadata generated and used by 'git svn'; they |
a81ed0b6 EW |
781 | *must* be set in the configuration file before any history is imported |
782 | and these settings should never be changed once they are set. | |
783 | ||
3e18ce1a JS |
784 | Additionally, only one of these options can be used per svn-remote |
785 | section because they affect the 'git-svn-id:' metadata line, except | |
786 | for rewriteRoot and rewriteUUID which can be used together. | |
e8f5d908 | 787 | |
448c81b4 | 788 | |
112f6385 SV |
789 | BASIC EXAMPLES |
790 | -------------- | |
3397f9df | 791 | |
92166fd7 SL |
792 | Tracking and contributing to the trunk of a Subversion-managed project |
793 | (ignoring tags and branches): | |
3397f9df | 794 | |
20b1d700 | 795 | ------------------------------------------------------------------------ |
a81ed0b6 | 796 | # Clone a repo (like git clone): |
2670ddce | 797 | git svn clone http://svn.example.com/project/trunk |
a81ed0b6 EW |
798 | # Enter the newly cloned directory: |
799 | cd trunk | |
647ac702 | 800 | # You should be on master branch, double-check with 'git branch' |
a81ed0b6 | 801 | git branch |
2de9b711 | 802 | # Do some work and commit locally to Git: |
a81ed0b6 EW |
803 | git commit ... |
804 | # Something is committed to SVN, rebase your local changes against the | |
805 | # latest changes in SVN: | |
b1889c36 | 806 | git svn rebase |
2de9b711 | 807 | # Now commit your changes (that were committed previously using Git) to SVN, |
a81ed0b6 | 808 | # as well as automatically updating your working HEAD: |
b1889c36 | 809 | git svn dcommit |
2de9b711 | 810 | # Append svn:ignore settings to the default Git exclude file: |
b1889c36 | 811 | git svn show-ignore >> .git/info/exclude |
20b1d700 | 812 | ------------------------------------------------------------------------ |
3397f9df | 813 | |
0d313b2b EW |
814 | Tracking and contributing to an entire Subversion-managed project |
815 | (complete with a trunk, tags and branches): | |
0d313b2b EW |
816 | |
817 | ------------------------------------------------------------------------ | |
92166fd7 | 818 | # Clone a repo with standard SVN directory layout (like git clone): |
7091a2d0 | 819 | git svn clone http://svn.example.com/project --stdlayout --prefix svn/ |
92166fd7 | 820 | # Or, if the repo uses a non-standard directory layout: |
7091a2d0 | 821 | git svn clone http://svn.example.com/project -T tr -b branch -t tag --prefix svn/ |
a81ed0b6 EW |
822 | # View all branches and tags you have cloned: |
823 | git branch -r | |
5de70efb | 824 | # Create a new branch in SVN |
3c123fb8 | 825 | git svn branch waldo |
a81ed0b6 EW |
826 | # Reset your master to trunk (or any other branch, replacing 'trunk' |
827 | # with the appropriate name): | |
7091a2d0 | 828 | git reset --hard svn/trunk |
a81ed0b6 | 829 | # You may only dcommit to one branch/tag/trunk at a time. The usage |
20f50f16 | 830 | # of dcommit/rebase/show-ignore should be the same as above. |
0d313b2b EW |
831 | ------------------------------------------------------------------------ |
832 | ||
647ac702 | 833 | The initial 'git svn clone' can be quite time-consuming |
7d4aef40 AR |
834 | (especially for large Subversion repositories). If multiple |
835 | people (or one person with multiple machines) want to use | |
647ac702 YD |
836 | 'git svn' to interact with the same Subversion repository, you can |
837 | do the initial 'git svn clone' to a repository on a server and | |
838 | have each person clone that repository with 'git clone': | |
7d4aef40 AR |
839 | |
840 | ------------------------------------------------------------------------ | |
841 | # Do the initial import on a server | |
7091a2d0 | 842 | ssh server "cd /pub && git svn clone http://svn.example.com/project [options...]" |
2b0d1033 SV |
843 | # Clone locally - make sure the refs/remotes/ space matches the server |
844 | mkdir project | |
845 | cd project | |
b1889c36 | 846 | git init |
2b0d1033 | 847 | git remote add origin server:/pub/project |
9cfdbf9b | 848 | git config --replace-all remote.origin.fetch '+refs/remotes/*:refs/remotes/*' |
2b0d1033 | 849 | git fetch |
2de9b711 | 850 | # Prevent fetch/pull from remote Git server in the future, |
9cfdbf9b S |
851 | # we only want to use git svn for future updates |
852 | git config --remove-section remote.origin | |
9e77353e JK |
853 | # Create a local branch from one of the branches just fetched |
854 | git checkout -b master FETCH_HEAD | |
7091a2d0 JH |
855 | # Initialize 'git svn' locally (be sure to use the same URL and |
856 | # --stdlayout/-T/-b/-t/--prefix options as were used on server) | |
857 | git svn init http://svn.example.com/project [options...] | |
7d4aef40 | 858 | # Pull the latest changes from Subversion |
b1889c36 | 859 | git svn rebase |
7d4aef40 AR |
860 | ------------------------------------------------------------------------ |
861 | ||
2eff1425 EW |
862 | REBASE VS. PULL/MERGE |
863 | --------------------- | |
2b26b65f JS |
864 | Prefer to use 'git svn rebase' or 'git rebase', rather than |
865 | 'git pull' or 'git merge' to synchronize unintegrated commits with a 'git svn' | |
866 | branch. Doing so will keep the history of unintegrated commits linear with | |
867 | respect to the upstream SVN repository and allow the use of the preferred | |
868 | 'git svn dcommit' subcommand to push unintegrated commits back into SVN. | |
869 | ||
870 | Originally, 'git svn' recommended that developers pulled or merged from | |
871 | the 'git svn' branch. This was because the author favored | |
483bc4f0 | 872 | `git svn set-tree B` to commit a single head rather than the |
2b26b65f JS |
873 | `git svn set-tree A..B` notation to commit multiple commits. Use of |
874 | 'git pull' or 'git merge' with `git svn set-tree A..B` will cause non-linear | |
875 | history to be flattened when committing into SVN and this can lead to merge | |
876 | commits unexpectedly reversing previous commits in SVN. | |
2e93115e | 877 | |
fd91d260 SS |
878 | MERGE TRACKING |
879 | -------------- | |
880 | While 'git svn' can track | |
bd43098c EW |
881 | copy history (including branches and tags) for repositories adopting a |
882 | standard layout, it cannot yet represent merge history that happened | |
883 | inside git back upstream to SVN users. Therefore it is advised that | |
2de9b711 | 884 | users keep history as linear as possible inside Git to ease |
bd43098c | 885 | compatibility with SVN (see the CAVEATS section below). |
1d52aba8 | 886 | |
7cad29d5 SL |
887 | HANDLING OF SVN BRANCHES |
888 | ------------------------ | |
889 | If 'git svn' is configured to fetch branches (and --follow-branches | |
2de9b711 | 890 | is in effect), it sometimes creates multiple Git branches for one |
e1c3bf49 | 891 | SVN branch, where the additional branches have names of the form |
7cad29d5 SL |
892 | 'branchname@nnn' (with nnn an SVN revision number). These additional |
893 | branches are created if 'git svn' cannot find a parent commit for the | |
894 | first commit in an SVN branch, to connect the branch to the history of | |
895 | the other branches. | |
896 | ||
897 | Normally, the first commit in an SVN branch consists | |
898 | of a copy operation. 'git svn' will read this commit to get the SVN | |
899 | revision the branch was created from. It will then try to find the | |
2de9b711 | 900 | Git commit that corresponds to this SVN revision, and use that as the |
7cad29d5 | 901 | parent of the branch. However, it is possible that there is no suitable |
2de9b711 | 902 | Git commit to serve as parent. This will happen, among other reasons, |
7cad29d5 SL |
903 | if the SVN branch is a copy of a revision that was not fetched by 'git |
904 | svn' (e.g. because it is an old revision that was skipped with | |
905 | '--revision'), or if in SVN a directory was copied that is not tracked | |
906 | by 'git svn' (such as a branch that is not tracked at all, or a | |
907 | subdirectory of a tracked branch). In these cases, 'git svn' will still | |
2de9b711 | 908 | create a Git branch, but instead of using an existing Git commit as the |
7cad29d5 | 909 | parent of the branch, it will read the SVN history of the directory the |
2de9b711 | 910 | branch was copied from and create appropriate Git commits. This is |
7cad29d5 SL |
911 | indicated by the message "Initializing parent: <branchname>". |
912 | ||
913 | Additionally, it will create a special branch named | |
914 | '<branchname>@<SVN-Revision>', where <SVN-Revision> is the SVN revision | |
915 | number the branch was copied from. This branch will point to the newly | |
916 | created parent commit of the branch. If in SVN the branch was deleted | |
917 | and later recreated from a different version, there will be multiple | |
918 | such branches with an '@'. | |
919 | ||
2de9b711 | 920 | Note that this may mean that multiple Git commits are created for a |
7cad29d5 SL |
921 | single SVN revision. |
922 | ||
923 | An example: in an SVN repository with a standard | |
924 | trunk/tags/branches layout, a directory trunk/sub is created in r.100. | |
925 | In r.200, trunk/sub is branched by copying it to branches/. 'git svn | |
2de9b711 | 926 | clone -s' will then create a branch 'sub'. It will also create new Git |
7cad29d5 | 927 | commits for r.100 through r.199 and use these as the history of branch |
2de9b711 | 928 | 'sub'. Thus there will be two Git commits for each revision from r.100 |
7cad29d5 SL |
929 | to r.199 (one containing trunk/, one containing trunk/sub/). Finally, |
930 | it will create a branch 'sub@200' pointing to the new parent commit of | |
931 | branch 'sub' (i.e. the commit for r.200 and trunk/sub/). | |
932 | ||
aabb2e51 EW |
933 | CAVEATS |
934 | ------- | |
935 | ||
fd91d260 SS |
936 | For the sake of simplicity and interoperating with Subversion, |
937 | it is recommended that all 'git svn' users clone, fetch and dcommit | |
647ac702 | 938 | directly from the SVN server, and avoid all 'git clone'/'pull'/'merge'/'push' |
2de9b711 TA |
939 | operations between Git repositories and branches. The recommended |
940 | method of exchanging code between Git branches and users is | |
647ac702 | 941 | 'git format-patch' and 'git am', or just 'dcommit'ing to the SVN repository. |
aabb2e51 | 942 | |
647ac702 | 943 | Running 'git merge' or 'git pull' is NOT recommended on a branch you |
fd91d260 | 944 | plan to 'dcommit' from because Subversion users cannot see any |
2de9b711 | 945 | merges you've made. Furthermore, if you merge or pull from a Git branch |
483bc4f0 | 946 | that is a mirror of an SVN branch, 'dcommit' may commit to the wrong |
aabb2e51 EW |
947 | branch. |
948 | ||
ce45a45f TR |
949 | If you do merge, note the following rule: 'git svn dcommit' will |
950 | attempt to commit on top of the SVN commit named in | |
951 | ------------------------------------------------------------------------ | |
952 | git log --grep=^git-svn-id: --first-parent -1 | |
953 | ------------------------------------------------------------------------ | |
954 | You 'must' therefore ensure that the most recent commit of the branch | |
955 | you want to dcommit to is the 'first' parent of the merge. Chaos will | |
956 | ensue otherwise, especially if the first parent is an older commit on | |
957 | the same SVN branch. | |
958 | ||
647ac702 YD |
959 | 'git clone' does not clone branches under the refs/remotes/ hierarchy or |
960 | any 'git svn' metadata, or config. So repositories created and managed with | |
961 | using 'git svn' should use 'rsync' for cloning, if cloning is to be done | |
aabb2e51 EW |
962 | at all. |
963 | ||
2de9b711 | 964 | Since 'dcommit' uses rebase internally, any Git branches you 'git push' to |
483bc4f0 | 965 | before 'dcommit' on will require forcing an overwrite of the existing ref |
aabb2e51 | 966 | on the remote repository. This is generally considered bad practice, |
483bc4f0 | 967 | see the linkgit:git-push[1] documentation for details. |
aabb2e51 | 968 | |
483bc4f0 | 969 | Do not use the --amend option of linkgit:git-commit[1] on a change you've |
aabb2e51 EW |
970 | already dcommitted. It is considered bad practice to --amend commits |
971 | you've already pushed to a remote repository for other users, and | |
972 | dcommit with SVN is analogous to that. | |
973 | ||
92166fd7 SL |
974 | When cloning an SVN repository, if none of the options for describing |
975 | the repository layout is used (--trunk, --tags, --branches, | |
2de9b711 | 976 | --stdlayout), 'git svn clone' will create a Git repository with |
92166fd7 SL |
977 | completely linear history, where branches and tags appear as separate |
978 | directories in the working copy. While this is the easiest way to get a | |
979 | copy of a complete repository, for projects with many branches it will | |
980 | lead to a working copy many times larger than just the trunk. Thus for | |
981 | projects using the standard directory structure (trunk/branches/tags), | |
982 | it is recommended to clone with option '--stdlayout'. If the project | |
983 | uses a non-standard structure, and/or if branches and tags are not | |
984 | required, it is easiest to only clone one directory (typically trunk), | |
985 | without giving any repository layout options. If the full history with | |
986 | branches and tags is required, the options '--trunk' / '--branches' / | |
987 | '--tags' must be used. | |
988 | ||
647ac702 | 989 | When using multiple --branches or --tags, 'git svn' does not automatically |
ab81a364 MB |
990 | handle name collisions (for example, if two branches from different paths have |
991 | the same name, or if a branch and a tag have the same name). In these cases, | |
2de9b711 | 992 | use 'init' to set up your Git repository then, before your first 'fetch', edit |
6fe7a30a KK |
993 | the $GIT_DIR/config file so that the branches and tags are associated |
994 | with different name spaces. For example: | |
ab81a364 MB |
995 | |
996 | branches = stable/*:refs/remotes/svn/stable/* | |
997 | branches = debug/*:refs/remotes/svn/debug/* | |
998 | ||
3397f9df EW |
999 | BUGS |
1000 | ---- | |
e8f5d908 | 1001 | |
a81ed0b6 EW |
1002 | We ignore all SVN properties except svn:executable. Any unhandled |
1003 | properties are logged to $GIT_DIR/svn/<refname>/unhandled.log | |
3397f9df | 1004 | |
2de9b711 | 1005 | Renamed and copied directories are not detected by Git and hence not |
bbe0c9b8 EW |
1006 | tracked when committing to SVN. I do not plan on adding support for |
1007 | this as it's quite difficult and time-consuming to get working for all | |
2de9b711 | 1008 | the possible corner cases (Git doesn't do it, either). Committing |
fd91d260 | 1009 | renamed and copied files is fully supported if they're similar enough |
2de9b711 | 1010 | for Git to detect them. |
bbe0c9b8 | 1011 | |
dd465ce6 SL |
1012 | In SVN, it is possible (though discouraged) to commit changes to a tag |
1013 | (because a tag is just a directory copy, thus technically the same as a | |
1014 | branch). When cloning an SVN repository, 'git svn' cannot know if such a | |
1015 | commit to a tag will happen in the future. Thus it acts conservatively | |
1016 | and imports all SVN tags as branches, prefixing the tag name with 'tags/'. | |
1017 | ||
a836a0e1 EW |
1018 | CONFIGURATION |
1019 | ------------- | |
1020 | ||
647ac702 | 1021 | 'git svn' stores [svn-remote] configuration information in the |
6fe7a30a | 1022 | repository $GIT_DIR/config file. It is similar the core Git |
a836a0e1 EW |
1023 | [remote] sections except 'fetch' keys do not accept glob |
1024 | arguments; but they are instead handled by the 'branches' | |
1025 | and 'tags' keys. Since some SVN repositories are oddly | |
1026 | configured with multiple projects glob expansions such those | |
1027 | listed below are allowed: | |
1028 | ||
1029 | ------------------------------------------------------------------------ | |
1030 | [svn-remote "project-a"] | |
1031 | url = http://server.org/svn | |
0e5e69a3 | 1032 | fetch = trunk/project-a:refs/remotes/project-a/trunk |
a836a0e1 EW |
1033 | branches = branches/*/project-a:refs/remotes/project-a/branches/* |
1034 | tags = tags/*/project-a:refs/remotes/project-a/tags/* | |
a836a0e1 EW |
1035 | ------------------------------------------------------------------------ |
1036 | ||
4ddef0e6 | 1037 | Keep in mind that the '\*' (asterisk) wildcard of the local ref |
d37a8de0 | 1038 | (right of the ':') *must* be the farthest right path component; |
bad542f0 | 1039 | however the remote wildcard may be anywhere as long as it's an |
02783075 | 1040 | independent path component (surrounded by '/' or EOL). This |
a836a0e1 | 1041 | type of configuration is not automatically created by 'init' and |
647ac702 | 1042 | should be manually entered with a text-editor or using 'git config'. |
a836a0e1 | 1043 | |
07576208 JS |
1044 | It is also possible to fetch a subset of branches or tags by using a |
1045 | comma-separated list of names within braces. For example: | |
1046 | ||
1047 | ------------------------------------------------------------------------ | |
1048 | [svn-remote "huge-project"] | |
1049 | url = http://server.org/svn | |
1050 | fetch = trunk/src:refs/remotes/trunk | |
7091a2d0 JH |
1051 | branches = branches/{red,green}/src:refs/remotes/project-a/branches/* |
1052 | tags = tags/{1.0,2.0}/src:refs/remotes/project-a/tags/* | |
07576208 JS |
1053 | ------------------------------------------------------------------------ |
1054 | ||
eff714bd NG |
1055 | Multiple fetch, branches, and tags keys are supported: |
1056 | ||
1057 | ------------------------------------------------------------------------ | |
1058 | [svn-remote "messy-repo"] | |
1059 | url = http://server.org/svn | |
1060 | fetch = trunk/project-a:refs/remotes/project-a/trunk | |
1061 | fetch = branches/demos/june-project-a-demo:refs/remotes/project-a/demos/june-demo | |
1062 | branches = branches/server/*:refs/remotes/project-a/branches/* | |
1063 | branches = branches/demos/2011/*:refs/remotes/project-a/2011-demos/* | |
1064 | tags = tags/server/*:refs/remotes/project-a/tags/* | |
1065 | ------------------------------------------------------------------------ | |
1066 | ||
7d82b4af JN |
1067 | Creating a branch in such a configuration requires disambiguating which |
1068 | location to use using the -d or --destination flag: | |
1069 | ||
1070 | ------------------------------------------------------------------------ | |
1071 | $ git svn branch -d branches/server release-2-3-0 | |
1072 | ------------------------------------------------------------------------ | |
1073 | ||
07576208 JS |
1074 | Note that git-svn keeps track of the highest revision in which a branch |
1075 | or tag has appeared. If the subset of branches or tags is changed after | |
6fe7a30a KK |
1076 | fetching, then $GIT_DIR/svn/.metadata must be manually edited to remove |
1077 | (or reset) branches-maxRev and/or tags-maxRev as appropriate. | |
07576208 | 1078 | |
945b9c14 KK |
1079 | FILES |
1080 | ----- | |
1081 | $GIT_DIR/svn/\*\*/.rev_map.*:: | |
1082 | Mapping between Subversion revision numbers and Git commit | |
1083 | names. In a repository where the noMetadata option is not set, | |
1084 | this can be rebuilt from the git-svn-id: lines that are at the | |
1085 | end of every commit (see the 'svn.noMetadata' section above for | |
1086 | details). | |
1087 | + | |
1088 | 'git svn fetch' and 'git svn rebase' automatically update the rev_map | |
1089 | if it is missing or not up to date. 'git svn reset' automatically | |
1090 | rewinds it. | |
1091 | ||
2e93115e EW |
1092 | SEE ALSO |
1093 | -------- | |
5162e697 | 1094 | linkgit:git-rebase[1] |
6ea922d5 JK |
1095 | |
1096 | GIT | |
1097 | --- | |
1098 | Part of the linkgit:git[1] suite |