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

Hi Maggie,

I'm a little confused. I checked the instructions for how to build

You do not need to build LibreOffice in order to work on the website.
You also do not need Cygwin to work on the website. For working on the
website, you only need the website repository. After installing Git,
you should have a Git GUI link in your start menu. Start that, click
on Clone existing repository, use
for Source Location, as the Target Directory use something like
C:\Users\(name)\git\ . Click on Clone, then wait some time.
Afterwards, use a file manager to navigate to the target directory.
Under "bug," you'll find the bug submission assistant.

You can also use the Git GUI tool to create a "commit" (i. e. a
versioned code change/"changeset"): for that, do the change in a
change using e.g. a text editor, then in Git GUI,  click Rescan, next
Change Stage (on the command line that would be: "git add ."), enter a
commit message and then click Commit (= "git commit").

However, if you'd rather work on mock-ups first, that's of course fine, too!

(If you still want to build LibreOffice: the recommendation is to do
that on Linux, as it is reasonably easy there. On Windows, getting to
a successful build can mean a lot of hit and miss and thus take some


Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.