Forums : Feedback Forum
Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.synopsys.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
[email protected]
Continuation enlistments
Hi,
I don't know if I am the first to have this idea, but for practical reasons it would be good if the project managers could mark one enlistment as a continuation of another one.
To illustrate this, consider the HelenOS project. It has two enlistments. One is a mercurial repository with old history converted from Subversion. The other one is the current Bazaar repository. We didn't attempt to convert our Subversion history to Bazaar, because it would not be a faithful conversion and therefore decided to start from scratch.
So now it looks like we have approximately twice as much code than we really have, counted for both the Mercurial and Bazaar repositories. We need to keep the Mercurial repo around because it contains our old history converted from Subversion.
Jakub
Hi Jakub,
This is a good idea. We've tossed around the idea of retiring
a repository, so that its net lines of code are no longer counted, but the idea of specifying continuation makes the relationship much more explicit.
I have to admit it will probably be a long time before we have time to implement a feature like this, but I like this idea.
Thanks,
Robin
