Subject: Re: [boost] [githelp] Relative submodule paths..
From: Edward Diener (eldiener_at_[hidden])
Date: 2015-02-06 21:12:18
On 2/6/2015 4:25 PM, Rene Rivera wrote:
> I've been trying to clean out the pull requests for the boost super-project
> and I ran into this one <https://github.com/boostorg/boost/pull/33>. And I
> don't really know if it makes sense, as I have personally not done a fork
> of the super-project.
> Is it a real problem? Should we change all the sub-project references? If
> yes, what are the likely impacts on others and existing release processes?
I assume a relative submodule URL refers to the path off of the
super-project's URL. As long as the super-project fork is done from
within Github the pull request is correct.
The way you have it designated works well if someone forks the
super-project and then forks all the sub-projects to URLs relative to
the forked super-project. I think this is an unlikely scenario. A forked
super-project will almost certainly want to refer to the existing
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk