On 7/22/2015 4:18 AM, Laszlo Ersek wrote:
How about someone creates a temporary branch off the github master branch, and applies all new patches from the list that have been reviewed thus far? Then once SVN is back up, the patches from that git branch could be committed to SVN by a single person, in one go, nicely ordered.
Wouldn't a fork be preferable? Anyone can create one, and it doesn't pollute the main repository.
SF have posted an update (http://sourceforge.net/blog/sourceforge-infrastructure-and-service-restoration-update-for-722/):
- SourceForge Allura Git service –*offline*, filesystem checks complete, all project data restored, data validation (repository presence check 100%, repository data presence check 100%, ‘git fsck’ of 10% representative from non-empty repositories 100%). Git validation was aided by its feature set. Final data validation pending and_ETA 7/22_ for resumption of service.
- SourceForge Allura Mercurial (Hg) service –*offline*, filesystem checks complete, all project data restored. Data validation (repository presence check, repository data presence check, and repository validation to occur and_ETA 7/23_ for service resumption.
- SourceForge Allura Subversion (SVN) service –*offline,*filesystem checks complete, data restoration at 50%. Restoration priority after Git and Hg services. _ETA TBD_, Future update will provide ETA.
- SourceForge non-Allura SCM platforms and CVS service –*offline,*filesystems checks and data restoration have not commenced. Priority given to modern SCMs which include internal data validation mechanisms; and those repositories fully backed by Apache Allura. Service restoration_ETA TBD_.
-- Bruce _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
