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