From: "Emmet Hikory" <emmet.hikory@gmail.com>
To: ecos-maintainers@ecos.sourceware.org
Subject: Patch selection for porting configtool to wxwidgets2.6
Date: Tue, 15 May 2007 06:31:00 -0000 [thread overview]
Message-ID: <9bd2f8970705142331m5dbfcc37x2f42ca735fd4bfb6@mail.gmail.com> (raw)
eCos Maintainers,
I am working on a project to remove all remaining dependencies on
wxwindows 2.4 from Ubuntu. Looking through the eCos mailing lists, I
have encountered two candidate patches that would migrate the
configtool to wxwidgets2.6, as follows:
1) http://www.xylanta.com/Content/Downloads/eCos/ct_wx260.zip from
Andy Jackson
2) http://www.mr.inf.tu-dresden.de/eCos/ct060628.patch.gz from Lars Poeschel
Neither appears to have been committed to CVS, and I wondered if
there were any specific problems with either patch implementation, and
also which might be a better starting point when applying a patch for
use in Ubuntu.
Thank you for your advice.
--
Emmet HIKORY
next reply other threads:[~2007-05-15 6:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 6:31 Emmet Hikory [this message]
2007-05-15 7:39 ` John Dallaway
2007-05-15 8:07 ` Emmet Hikory
2007-05-15 8:27 ` John Dallaway
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=9bd2f8970705142331m5dbfcc37x2f42ca735fd4bfb6@mail.gmail.com \
--to=emmet.hikory@gmail.com \
--cc=ecos-maintainers@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).