public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Aldy Hernandez <aldyh@redhat.com>
To: George France <france@handhelds.org>
Cc: Alexandre Oliva <aoliva@redhat.com>,
	Matthew H Bemis <bemis@iol.unh.edu>,
	gcc@gcc.gnu.org, cgf@redhat.com
Subject: Re: Missing Directory in CVS tree
Date: Mon, 03 Dec 2001 13:50:00 -0000	[thread overview]
Message-ID: <1007416354.16033.27.camel@litecycle.cc.andrews.edu> (raw)
In-Reply-To: <01120312451300.18456@shadowfax.middleearth>

On Mon, 2001-12-03 at 09:45, George France wrote:
> On Friday 30 November 2001 14:45, Alexandre Oliva wrote:
> > On Nov 30, 2001, Matthew H Bemis <bemis@iol.unh.edu> wrote:
> > > for the basic toolchain build there is a file called texi2pod.pl that is
> > > in contrib, but when the toolchain is built the process is looking for
> > > ../etc/texi2pod.pl
> >
> > It seems that the problem you've encountered is in the binutils build
> > procedure, so you got the wrong mailing list.  etc is part of the
> > binutils source tarball, so there's no problem in binutils either.
> 
> Greetings,
> 
> I believe that he is reffering to the uberbaum cvs repository from message of 
> Nov 28, 2001 by Aldy Hernandez. The uberbaum repository is missing 'etc'. :-)
> 
> http://gcc.gnu.org/ml/gcc/2001-11/msg01521.html
> 
> 
> Does anybody know who is the uberbaum maintainer??

chris faylor (cgf@redhat.com)

what i would REALLY like is if i could actually commit through the
uberbaum tree.

-- 
Aldy Hernandez			E-mail: aldyh@redhat.com
Professional Gypsy
Red Hat, Inc.

  reply	other threads:[~2001-12-03 21:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-23 14:42 Matthew H Bemis
2001-11-23 16:03 ` Alexandre Oliva
2001-11-30 11:47   ` Alexandre Oliva
2001-12-03  9:50   ` George France
2001-12-03 13:50     ` Aldy Hernandez [this message]
2001-11-30 11:10 ` Matthew H Bemis

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=1007416354.16033.27.camel@litecycle.cc.andrews.edu \
    --to=aldyh@redhat.com \
    --cc=aoliva@redhat.com \
    --cc=bemis@iol.unh.edu \
    --cc=cgf@redhat.com \
    --cc=france@handhelds.org \
    --cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).