From: Dan Pop <Dan.Pop@cern.ch>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] toolchain status
Date: Mon, 20 Nov 2000 15:34:33 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205753@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205739@msgid-missing>
On Mon, 20 Nov 2000, Francis Galiegue wrote:
> On Fri, 17 Nov 2000, H . J . Lu wrote:
>
> > >
> > > I'm talking about GNU's stock glibc-2.2.tar.gz here... I didn't know there
> > > were CVS snapshots of it again. Where are they to be found?
> > >
> >
> > http://sources.redhat.com/glibc/
> >
>
> Hmmm, in snapshots/, the most recent I see is 2.1.3-pre4. This obviously is not
> the good one...
You've missed these bits from the URL above:
You can access the development source tree a couple of different ways.
Anonymous CVS read-only access
cvs -z 9 -d :pserver:anoncvs@anoncvs.cygnus.com:/cvs/glibc login
{enter "anoncvs" as the password}
cvs -z 9 -d :pserver:anoncvs@anoncvs.cygnus.com:/cvs/glibc co libc
Read-only web-based CVS access
You can use the cvsweb interface.
Dan
prev parent reply other threads:[~2000-11-20 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-17 14:55 [Linux-ia64] toolchain status Francis Galiegue
2000-11-17 17:01 ` H . J . Lu
2000-11-17 17:26 ` H . J . Lu
2000-11-17 17:29 ` Francis Galiegue
2000-11-20 9:56 ` Francis Galiegue
2000-11-20 15:34 ` Dan Pop [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590678205753@msgid-missing \
--to=dan.pop@cern.ch \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox