[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-gnulib] gnulib web page
|
From: |
Jeff Bailey |
|
Subject: |
Re: [Bug-gnulib] gnulib web page |
|
Date: |
Wed, 22 Jan 2003 18:17:11 -0800 |
|
User-agent: |
Mutt/1.3.28i |
How are you trying to edit this? I'm confused by your reference to
"www".
Checkout the following with CVS:
cvs -d :ext:address@hidden:/webcvs co software/gnulib
If that doesn't work, can you paste errors to me? The permissions all
look like they're setup correctly.
Thanks for updating this!
Tks,
Jeff Bailey
On Wed, Jan 22, 2003 at 08:56:19PM -0500, Karl Berry wrote:
> I revised the gnulib home page (see below, any comments?), but don't
> have write permission to www/software/gnulib.
>
> Jeff, help? I can't see any way to give myself permission on the admin
> page. Am I supposed to request this of savannah-hackers, or can you do it?
>
> Thanks,
> karl
>
>
> <html>
> <!-- $Id$ -->
> <head>
> <title>GNULib - GNU Portability Library - GNU Project - Free Software
> Foundation (FSF)</title>
> <link REV="made" HREF="mailto:address@hidden";>
> <meta NAME="keywords" CONTENT="portability, library, source sharing">
> </head>
> <body BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#1F00FF" ALINK="#FF0000"
> VLINK="#9900DD">
>
> <a HREF="/graphics/gnu-head-sm.jpg"><img SRC="/graphics/gnu-head-sm.jpg"
> ALT=" [image of the Head of a GNU] "
> WIDTH="129" HEIGHT="122"> (jpeg 7k)</a>
> <a HREF="/graphics/gnu-head.jpg">(jpeg 21k)</a>
> <a HREF="/philosophy/gif.html">no gifs due to patent problems</a>
>
> <h2>GNULib - The GNU Portability Library</h2>
>
> <p>GNU software has a well-deserved reputation for running on many
> different types of systems. While our primary goal is to write
> software for the GNU system, many users and developers have been
> introduced to us through the systems that they were already using.</p>
>
> <p>Until now, there was no central place for all of the special GNU
> versions to exist. <a href="http://gcc.gnu.org/";>GCC</a> has
> <a href="http://gcc.gnu.org/onlinedocs/libiberty/";>libiberty</a>, but
> this is hard to disentangle from the GCC build tree.
> <a href="http://www.iro.umontreal.ca/~pinard/libit/HTML/";>libit</a>
> proved too hard to keep up to date, and at this point is moribund.
>
> <p>Why, then, create another library? gnulib takes a different
> approach. Its components are intended to be shared at the source level,
> rather than being a library that gets installed and linked against.
> Instead, the idea is to copy files from gnulib into your own source
> tree.
>
> <p>You can
> <a href="http://savannah.gnu.org/cgi-bin/viewcvs/gnulib/gnulib/";>browse the
> current gnulib sources on
> <a href="http://savannah.gnu.org";>savannah</a>.<br>
> Or you can
> <a
> href="http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/gnulib/gnulib/MODULES.html?rev=HEAD&content-type=text/html";>view
> the modules comprising gnulib</a>.
>
> <p>To use gnulib, check out the sources via anonymous cvs (see
> instructions on the <a
> href="http://savannah.gnu.org/projects/gnulib/";>gnulib project page</a>
> if need be).
> Then run <tt>./gnulib-tool --help</tt>. For help or more info, email
> <a href="mailto:address@hidden";>address@hidden</a>. (We will
> post real documentation as soon as we've written some. :)
>
>
> <h3>How do I get my routines into gnulib?</h3>
>
> <p>Please email <a href="mailto:address@hidden";>address@hidden</a>
> with information. Here are some guidelines, however:</p>
>
> <ul>
> <li>If your .c and .h files define functions that are broken or missing
> on some other system, we should be able to include it.</li>
> <li>If your functions remove arbitrary limits from existing functions
> (either under the same name, or as a slightly different name), we should
> be able to include it.</li>
> <li>If your functions define completely new but rarely used
> functionality, you should probably consider packaging it as a seperate
> library.</li>
> </ul>
>
> <p>All source code is copylefted by the Free Software Foundation.
> Assignment forms may be necessary before we can access your source
> code.</p>
>
>
> <hr>
> <p>
> Return to <a HREF="/home.html">GNU's home page</a>.
>
> <p>
> Please send FSF & GNU inquiries & questions to
> <a HREF="mailto:address@hidden";><em>address@hidden</em></a>.
> There are also <a HREF="/home.html#ContactInfo">other ways to
> contact</a> the FSF.
> <p>
>
> Please send comments on these web pages to
> <a HREF="mailto:address@hidden";><em>address@hidden</em></a>,
> send other questions to
> <a HREF="mailto:address@hidden";><em>address@hidden</em></a>.
>
> <p>
> Copyright (C) 2003 Free Software Foundation, Inc.,
> 59 Temple Place - Suite 330, Boston, MA 02111, USA
>
> <p>
> Verbatim copying and distribution of this entire article is
> permitted in any medium, provided this notice is preserved.
> <p>
> Updated:
> <!-- timestamp start -->
> $Date: 2001/10/19 12:54:10 $ $Author: jbailey $
> <!-- timestamp end -->
> <hr>
> </body>
> </html>
>
>
> _______________________________________________
> Bug-gnulib mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-gnulib
>