Hi all,
[please follow up on projects@ list]
There is an planed effort to reduce and consolidate the number of git
repositories in use (up to 20 currently) and migrate them using a git
fetch, however it has some drawbacks with history being unusable.
A clean up will be necessary too (the main one being tab/space
clean-up). You'll find a C program for that indicated on the wiki page
bellow.
As a result also, the development pages will need to be updated on the
wiki, so you'll have to monitor the changes done there.
The script onegit.sh, which is located in contrib/dev-tools, implement
the steps described above.
The migration is intrusive so please, pay attention to what will be done
and the schedule (not confirm yet) on this page
http://wiki.documentfoundation.org/Development/One_Git_Conversion
Thanks in advance for your help, your feedback and your monitoring on this.
If you have any question, don't hesitate to ask (I am for sure the wrong
person to answer but I know where the resource is hiding :)
Kind regards
Sophie
--
Founding member of The Document Foundation
--
Unsubscribe instructions: E-mail to l10n+help@global.libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [libreoffice-l10n] Single Git repository migration plan · Sophie Gautier
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.