... | @@ -101,7 +101,7 @@ origin https://ohwr.org/project/spec-sw.git (push) |
... | @@ -101,7 +101,7 @@ origin https://ohwr.org/project/spec-sw.git (push) |
|
|
|
|
|
### What about submodules and submodule references?
|
|
### What about submodules and submodule references?
|
|
|
|
|
|
If you use submodules, you deserve what you get :)
|
|
If you use submodules, you deserve what you get :smile:.
|
|
More seriously, the change of repository URL risks breaking absolute submodule references. If at *any* commit in your repository, you have a submodule checked out with one of the old URL references, your build will fail.
|
|
More seriously, the change of repository URL risks breaking absolute submodule references. If at *any* commit in your repository, you have a submodule checked out with one of the old URL references, your build will fail.
|
|
To avoid this scenario, we have tried our best to keep mirrors of the old repositories at the same URLs as before. *These are read-only, non-pushable, volatile copies that are kept for backward compatibility only*.
|
|
To avoid this scenario, we have tried our best to keep mirrors of the old repositories at the same URLs as before. *These are read-only, non-pushable, volatile copies that are kept for backward compatibility only*.
|
|
This is the only way we have found till now to keep unbroken builds in case old repository URLs (and commits) are referenced. In particular, remote URLs with intermediate path components other than `/project/` are certain to be *invalid* for any other purpose than the uses former submodule references gave to them.
|
|
This is the only way we have found till now to keep unbroken builds in case old repository URLs (and commits) are referenced. In particular, remote URLs with intermediate path components other than `/project/` are certain to be *invalid* for any other purpose than the uses former submodule references gave to them.
|
... | | ... | |