From: Sergei Organov <osv@javad.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Public CVS ecos/images woe.
Date: Fri, 15 Feb 2008 12:44:00 -0000 [thread overview]
Message-ID: <fp41er$45c$1@ger.gmane.org> (raw)
Hello,
Is it possible to entirely get rid of those painful ecos/images
subdirectory (by moving it into separate module or something)?
The problem is that while it is indeed not checked out on initial
checkout of the 'ecos' module, the next
cvs update -d -P
brings it back into the working tree. Updating without -d is a bad idea
as it doesn't checkout new directories into the working tree when they
appear in the repository.
BTW, is there a way to get entire eCos public CVS *repository* in order
to mirror it locally?
-- Sergei.
--
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 reply other threads:[~2008-02-15 12:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 12:44 Sergei Organov [this message]
2008-02-15 13:24 ` [ECOS] " Daniel Néri
2008-02-15 14:02 ` Sergei Organov
2008-02-15 15:27 ` [ECOS] " Andrew Lunn
2008-02-15 16:36 ` [ECOS] " Sergei Organov
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='fp41er$45c$1@ger.gmane.org' \
--to=osv@javad.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).