[libreoffice-users] Re: Missing cups.h While Compiling (Linux)

NoOp <glgxg -AT- sbcglobal.net>
Mon, 12 Dec 2011 09:15:36 -0800

On 12/12/2011 07:58 AM, Joel Madero wrote:

How do I get on the developers list? Thanks

...
http://www.libreoffice.org/get-involved/developers/
"Primary points of contact and resources: the #libreoffice-dev channel
at irc.freenode.net, the Development wiki page, and the developers
mailing list at FreeDesktop, please read these notes before posting."
http://lists.freedesktop.org/mailman/listinfo/libreoffice



-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context

[libreoffice-users] Missing cups.h While Compiling (Linux) · Joel Madero
- Re: [libreoffice-users] Missing cups.h While Compiling (Linux) · Jay Lozier
  - Re: [libreoffice-users] Missing cups.h While Compiling (Linux) · Joel Madero
    - Re: [libreoffice-users] Missing cups.h While Compiling (Linux) · Jay Lozier
- Re: [libreoffice-users] Missing cups.h While Compiling (Linux) · webmaster for Kracked Press Productions
  - Re: [libreoffice-users] Missing cups.h While Compiling (Linux) · Joel Madero
    - [libreoffice-users] Re: Missing cups.h While Compiling (Linux) · NoOp

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.