From: Grant Edwards <grante@visi.com>
To: eCos Discussion <ecos-discuss@sources.redhat.com>
Subject: [ECOS] Keeping 2.0 source tree up to date
Date: Mon, 22 Sep 2003 14:44:00 -0000 [thread overview]
Message-ID: <20030922094312.A14731@visi.com> (raw)
Whats the recommended way to keep a 2.0 source tree up to date
with bug fixes?
Do I need to try to get BOFH to allow access to the CVS tree?
Is there an official archive of approved patches somewhere that
can be downloaded?
--
Grant Edwards
grante@visi.com
--
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 reply other threads:[~2003-09-22 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 14:44 Grant Edwards [this message]
2003-09-22 15:17 ` Andrew Lunn
2003-09-22 18:59 ` Grant Edwards
2003-09-22 19:11 ` Gary Thomas
2003-09-22 19:20 ` Grant Edwards
2003-09-22 19:29 ` Gary Thomas
2003-09-22 19:34 ` Grant Edwards
2003-09-23 11:03 Reinhard JESSICH
2003-09-29 15:50 ` Roland Caßebohm
2003-09-23 11:32 David Vrabel
[not found] <sf787ac4.077@mail.frequentis.com>
2003-09-29 16:37 ` Roland Caßebohm
2003-09-30 3:16 Reinhard JESSICH
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=20030922094312.A14731@visi.com \
--to=grante@visi.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).