From: Andrew Lunn <andrew@lunn.ch>
To: Bronislav Gabrhelik <bgabrhelik@ahojky.com>
Cc: ecos-discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] the ecos/packages/hal/common is missing for ecos-arm cvs alias module
Date: Mon, 19 Nov 2007 01:08:00 -0000 [thread overview]
Message-ID: <20071118215214.GA4933@lunn.ch> (raw)
In-Reply-To: <3d344cfe0711181343r7bef7dednc8e5bca56b61b6f2@mail.gmail.com>
On Sun, Nov 18, 2007 at 10:43:51PM +0100, Bronislav Gabrhelik wrote:
> Hi all,
>
> I am not sure if it is not bug in cvs client for windows platform, but
> when I check out ecos-arm cvs module the ecos/packages/hal/common and
> ecos/packages/hal/arm directories are empty. I tried both to me
> available versions : the cygwin's cvs and cvsnt. It seems to me like
> !ecos/packages/hal has bigger preference. I develop only for Arm so I
> would like to minimize the amount of source files to maintain.
We have never allowed partial checkouts. You need to get everything.
at least to start with. Once you have everything checked out, you
could then in theory delete parts you don't need. Remember to also
edit your ecos.db file to remove packages you delete.
> What is the common practice? Should I use different module? Is it
> somewhere documented?
Using anoncvs is documented at:
http://ecos.sourceware.org/anoncvs.html
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2007-11-18 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-18 21:52 Bronislav Gabrhelik
2007-11-19 1:08 ` Andrew Lunn [this message]
2007-11-19 12:15 ` Bronislav Gabrhelik
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=20071118215214.GA4933@lunn.ch \
--to=andrew@lunn.ch \
--cc=bgabrhelik@ahojky.com \
--cc=ecos-discuss@ecos.sourceware.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).