From: Grant Edwards <grante@visi.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: Splitting the eCos repository
Date: Fri, 11 Aug 2006 16:08:00 -0000 [thread overview]
Message-ID: <20060811160806.1B48654397@rivatek.dnsalias.net> (raw)
In-Reply-To: <c09652430608110801o726a062dsabf80d8ebbc948f7@mail.gmail.com>
In gmane.os.ecos.general, you wrote:
>> I'd say not before configtool supports it. But it would also
>> make creating a public "experimental" repository possible
>> (e.g. on sourceforge) for stuff which didn't make it yet into
>> the main repository.
>
> I'm starting to think that the configtool is doing non-trivial
> damage to eCos.
Besides, configtool makes it all look too easy. ;)
--
Grant Edwards grante Yow! .. I
at feel... JUGULAR...
visi.com
--
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:[~2006-08-11 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 14:54 AW: [ECOS] " Neundorf, Alexander
2006-08-11 15:01 ` Øyvind Harboe
2006-08-11 16:08 ` Grant Edwards [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-11 9:24 Øyvind Harboe
2006-08-11 16:06 ` [ECOS] " Grant Edwards
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=20060811160806.1B48654397@rivatek.dnsalias.net \
--to=grante@visi.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).