Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


On Mon, Jul 4, 2011 at 10:14 PM, Sophie Gautier
<gautier.sophie@gmail.com> wrote:
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 :)


Once the migration takes place, each person should clone this single
Git repository, right?

Is it possible to create a tarball of the repository so that people
can download using a download manager (through HTTP or FTP), and then
they can 'git pull' in order to bring in sync?

Simos

Context


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.