You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 0b90a1e
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: doc/subtree.md
+29Lines changed: 29 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,3 +11,32 @@ The procedure for performing subtree synchronizations is documented [here][rdg-j
11
11
## Pushing changes to `rust-lang/rust`
12
12
13
13
If the used GCC commit (recorded in `libgccjit.version`) changed in `rustc_codegen_gcc`, then you will have to update the `gcc` submodule in the `rust-lang/rust` repository in the push sync PR. The CI in `rust-lang/rust` should ensure that these two commit references match. You can simply update the `gcc` submodule commit and push it to your push sync PR once it has been created.
14
+
15
+
## Environment variables to make things easier
16
+
17
+
To avoid passing through github `https` interface, create a file named `josh.gitconfig` (for example at `$HOME/.config/git/josh.gitconfig`) which contains:
18
+
19
+
```gitconfig
20
+
[url "git@github.com:"]
21
+
insteadOf="https://github.com/"
22
+
23
+
[include]
24
+
path=~/.gitconfig
25
+
path=~/.config/git/config
26
+
```
27
+
28
+
Then refer to it using the `GIT_CONFIG_GLOBAL` environment variable.
29
+
30
+
And to prevent cloning the rust repository every time, set the `RUSTC_GIT` environment variable to point to your local copy of the `rust` repository. The path needs to be absolute!
0 commit comments