From: Jonathan Larmour <jifl@eCosCentric.com>
To: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: ecos-opt
Date: Wed, 21 May 2003 19:31:00 -0000 [thread overview]
Message-ID: <3ECBD40B.1080501@eCosCentric.com> (raw)
Now that 2.0 is out and for the moment we hope, people will be less
reliant on CVS (or at least there won't be a much better time), I would
like to do something a little drastic...
As (ex-)Red Hat folks will remember, it was decided way way back to split
off the network stack and SNMP directories into a separate "ecos-opt"
hierarchy in the public CVS tree. And so it has remained to this day.
However I've found I still get the odd problems because of this, in
particular if you use "checkout" as a way to update your source tree,
instead of "update" it barfs.
So I'd like to finally bring everything back into one tree. I believe it
can be done fairly easily, by just moving the directories into place
within the repository and then putting in symlinks directly in the CVS
repository in the old places to make sure existing checkouts work.... but
new checkouts would not get those as I would update the "modules" file
appropriately. It would only really affect things for people using
"checkout" to update their sources, but since that's already broken there
can't be many of those :-).
Any objections or suggestions? If not, I'll choose a quiet period some
time soon to do it.... as you can tell actually doing it is just a few
trivial commands actually! But of course I'll need to test it.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
next reply other threads:[~2003-05-21 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-21 19:31 Jonathan Larmour [this message]
2003-05-21 19:34 ` ecos-opt Gary Thomas
2003-05-22 7:31 ` ecos-opt Andrew Lunn
2003-05-22 10:43 ` ecos-opt Jonathan Larmour
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=3ECBD40B.1080501@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-maintainers@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).