Subversion repository closed for all commits on all branches
The Subversion repository is now closed for all commits on all branches. An attempt to commit will fail a pre-commit hook, resulting in the following error message: Command: Commit Modified: C:\boost\trunk\libs\system\doc\index.html Sending content: C:\boost\trunk\libs\system\doc\index.html Error: Commit failed (details follow): Error: Commit blocked by pre-commit hook (exit code 1) with output: Error: This Subversion repository is no longer in active use. Error: Error: It has been superseded by a Git super-project repository Error: and individual Git repositories for each Boost library. Error: Error: See: https://github.com/boostorg Completed!: The next step in the conversion to Git and Modular Boost is to run the conversion script one last time, and then turn it off. We will let you know when that is completed. -- The Release Managers
On Sun, Nov 24, 2013 at 8:13 AM, Beman Dawes
The Subversion repository is now closed for all commits on all branches.
Perhaps it would make sense to switch the boost super-project from a forked repository to a normal repository? That would remove the "forked from har999y/boost" that appears on the boost super-project. If you make a request to GitHub I believe they can make the change. Superproject: https://github.com/boostorg/boost Removing "forked from": http://stackoverflow.com/questions/16052477/how-can-i-delete-fork-dependency... Cheers! Andrew Hundt
Andrew Hundt
On Sun, Nov 24, 2013 at 8:13 AM, Beman Dawes
wrote: The Subversion repository is now closed for all commits on all branches.
Perhaps it would make sense to switch the boost super-project from a forked repository to a normal repository? That would remove the "forked from har999y/boost" that appears on the boost super-project.
If you make a request to GitHub I believe they can make the change.
We've done that several times, IIRC. I think it's a GitHub bug. But please feel free to make the request.
Superproject: https://github.com/boostorg/boost
Removing "forked from": http://stackoverflow.com/questions/16052477/how-can-i-delete-fork-dependency...
Cheers! Andrew Hundt
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On Wed, Nov 27, 2013 at 11:30 AM, Dave Abrahams
Andrew Hundt
writes: Perhaps it would make sense to switch the boost super-project from a forked repository to a normal repository? That would remove the "forked from har999y/boost" that appears on the boost super-project.
If you make a request to GitHub I believe they can make the change.
We've done that several times, IIRC. I think it's a GitHub bug. But please feel free to make the request.
I don't believe I could make such a request unless my account (ahundt) was a member of the "boostorg" organization on GitHub. There is also an alternative solution where deleting the repository from GitHub then manually re-adding it will make it appear "fresh" from the perspective of GitHub. Of course that would have the unfortunate side effect of the repository not existing between when it is deleted and re-added, so it would probably require a brief announced and scheduled down time. http://www.quora.com/Git-revision-control/How-can-one-detach-a-forked-projec... Cheers! Andrew Hundt
participants (3)
-
Andrew Hundt
-
Beman Dawes
-
Dave Abrahams