From: Gary Thomas <gthomas@redhat.com>
To: "Koeller, T." <Thomas.Koeller@baslerweb.com>
Cc: eCos Discussion <ecos-discuss@sources.redhat.com>
Subject: Re: AW: [ECOS] redboot cannot be built without networking support
Date: Wed, 29 May 2002 09:46:00 -0000 [thread overview]
Message-ID: <1022690627.2835.141.camel@laptop_local> (raw)
In-Reply-To: <850597605E79D21182830008C7A4B9CF07D88940@COMM1>
On Wed, 2002-05-29 at 16:36, Koeller, T. wrote:
> Gary Thomas wrote:
>
> > On Wed, 2002-05-29 at 10:44, Koeller, T. wrote:
> > > > Note that with v2.0, the networking and DNS packages are included
> > > > with the mainline code base, so this is no longer a problem.
> > >
> > > I assumed the latest CVS _were_ v2.0?
> >
> > It is. Note that the standard "modules" set has changed a little
> > since the original announcement and a top level checkout will get
> > you those additional packages. Be sure and update with -d.
>
> I did - but still there is no 'net' branch, and consequently the
> references in ecos.db point to nonexisting directories.
>
Odd. I just updated an old, pre v_2.0, repository and it's all there.
Perhaps you have a sticky tag? or forgot -d? The command I used was:
cvs up -A -d -P
from the topmost (eCos/...) level.
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2002-05-29 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 8:39 Koeller, T.
2002-05-29 9:46 ` Gary Thomas [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-29 10:31 Koeller, T.
2002-05-30 1:33 ` Gary Thomas
[not found] <850597605E79D21182830008C7A4B9CF07D8893F@COMM1>
2002-05-29 2:54 ` Gary Thomas
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=1022690627.2835.141.camel@laptop_local \
--to=gthomas@redhat.com \
--cc=Thomas.Koeller@baslerweb.com \
--cc=ecos-discuss@sources.redhat.com \
/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).