... | ... | @@ -6,7 +6,7 @@ The information on this page is slightly out of date; see [GitRepoReorganization |
|
|
|
|
|
Many of the libraries and tools in a GHC tree are actually maintained by someone else. They therefore have a separate upstream repository, from which we need to pull. That repository may be either a darcs or a git repository; in the darcs case, we also need to convert to a git repository for use in a GHC tree. However, if the darcs repository is on another server, then we first need to mirror it for the conversion program to use. This diagram shows how changes migrate from one repo to another:
|
|
|
|
|
|
[](/trac/ghc/attachment/wiki/Repositories/Upstream/repos.png)
|
|
|
![](upstream/repos.png)
|
|
|
|
|
|
|
|
|
This means that when making changes needed in GHC to one of these libraries, we first need to put the changes in the upstream repository. Note that a git hook prevents you from pushing patches to the ghc repos until they are already in the git mirror repos, so that we cannot forget to send changes upstream.
|
... | ... | |