On 05/04/2016 01:10 PM, Brian (bex) Exelbierd wrote: > >> On May 4, 2016, at 10:01 PM, Corey Sheldon <sheldon.corey@xxxxxxxxxxxxxxx> wrote: >> >> Docs Team, >> >> >> As some of you have heard, within the next year or so >> https://fedorahosted.org/cgit/docs/ will be phased out in favor of >> https://pagure.io/group/fedora-docs. In the updating of things for >> F24 install-guide and such the team has decided to start early in >> migrating things over to pagure. Current workflow is to move over >> repos and request remotes be adjusted on your local forks (this will >> be roughly a week of time) then the fedorahosted repos will go R/O >> (read only). The goal behind this is not prevent current repos from >> breaking but also to alleviate the need for an additional massive sync >> later on. > > While I realize it creates a need for a new clone, could we consider the idea of trimming the repos? Several books contain a lot of data of old graphics and translations that make the initial clone very costly. This is a good chance to cut the fat, so to speak. > > regards, > > bex > >> >> >> The quick and dirty on how to relocate your remotes: >> >> >> git remote add new-origin ssh://git@xxxxxxxxx/{repo_name}.git >> >> git remote rm origin >> >> git remote rename new-origin origin >> >> >> Then all future changes will be on the pagure instance and pushes will >> also go there. >> >> >> >> >> --- Warm Regards --- >> Corey Sheldon >> P: +1 (310) 909 7672 >> PGP: B54B7228 (keybase) | 5A88E539 (personal) | D2264944 (fedora) >> https://gist.github.com/linux-modder/ac5dc6fa211315c633c9 >> >> Disclaimer: This document, including attachments, is intended for the >> person(s) named within and may contain confidential and/or legally >> privileged information, and may occasionally include Intellectual >> Property / Embargoed Content. it is request that all emails regardless >> of topic or content are regarded in this manner. Unauthorized >> disclosure, copying / distribution of this information may be unlawful >> and is prohibited, including unsolicited Cc/Bcc. If you are not the >> intended recipient, please disregard and destroy this message and if the >> recipient is known to you please inform them, and a return email >> indicating a improper recipient IS requested so that I may remove you >> from any lists, conversations such error may have created / allowed. Use >> of OpenGPG keys are highly encouraged my keys can be found @ >> hkp://keys.gnupg.net & hkp://keys.fedoraproject.org >> > > > > -- > docs mailing list > docs@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe: > http://lists.fedoraproject.org/admin/lists/docs@xxxxxxxxxxxxxxxxxxxxxxx > Bex, I'm game so long as we can get working docs out in time for GA, if you have any suggestions as pertain to security-guide/selinux-guide or multiboot I'm trying to trim and update those and am all ears. -- --- Warm Regards --- Corey Sheldon P: +1 (310) 909 7672 PGP: B54B7228 (keybase) | 5A88E539 (personal) | D2264944 (fedora) https://gist.github.com/linux-modder/ac5dc6fa211315c633c9 Disclaimer: This document, including attachments, is intended for the person(s) named within and may contain confidential and/or legally privileged information, and may occasionally include Intellectual Property / Embargoed Content. it is request that all emails regardless of topic or content are regarded in this manner. Unauthorized disclosure, copying / distribution of this information may be unlawful and is prohibited, including unsolicited Cc/Bcc. If you are not the intended recipient, please disregard and destroy this message and if the recipient is known to you please inform them, and a return email indicating a improper recipient IS requested so that I may remove you from any lists, conversations such error may have created / allowed. Use of OpenGPG keys are highly encouraged my keys can be found @ hkp://keys.gnupg.net & hkp://keys.fedoraproject.org
Attachment:
signature.asc
Description: OpenPGP digital signature
-- docs mailing list docs@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: http://lists.fedoraproject.org/admin/lists/docs@xxxxxxxxxxxxxxxxxxxxxxx
