From: John Dallaway <jld@ecoscentric.com>
To: Andy Jackson <ecos@xylanta.com>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: wxWidgets tool
Date: Mon, 05 Nov 2007 10:24:00 -0000 [thread overview]
Message-ID: <472EEF5E.2060308@ecoscentric.com> (raw)
Hi Andy
Have you been able to make any progress with the copyright assignment? I
have been looking at some other configtool patches for unicode support
and would like to be able to commit your patches for building against
wxWidgets 2.6 first.
John Dallaway
-------- Original Message --------
Subject: Re: Re: wxWidgets tool
Date: Tue, 2 Oct 2007 15:07:56 +0100
From: Andy Jackson <ecos@xylanta.com>
Reply-To: Andy Jackson <ecos@xylanta.com>
To: <ecos-discuss@ecos.sourceware.org>
CC: John Dallaway <jld@ecoscentric.com>
Newsgroups: gmane.os.ecos.general
----- Original Message -----
From: "John Dallaway" <jld@ecoscentric.com>
To: "Tom Malcolmson" <tom@malcolmson.com>
Cc: <ecos-discuss@ecos.sourceware.org>
Sent: Tuesday, October 02, 2007 9:30 AM
Subject: [ECOS] Re: wxWidgets tool
> Tom
>
> Tom Malcolmson wrote:
>
>> I noticed some patches available here:
>> http://www.xylanta.com/WordPress/?page_id=22
>> including one to make it work with wxWidgets v2.6.
>
> Coincidentally, I have recently tracked down an issue with the eCos
> Configuration Tool when built against wxGTK 2.6.x on Linux. The Xylanta
> patches will be checked-in when the necessary copyright assignment is in
> place.
Apologies, I've been away and will try and sort the assignment out this
week,
Andy..
next reply other threads:[~2007-11-05 10:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 10:24 John Dallaway [this message]
2007-11-05 11:40 ` Andy Jackson
2007-11-05 13:07 ` Jonathan Larmour
2007-11-05 13:24 ` Andrew Lunn
2007-11-05 13:45 ` Nick Garnett
2007-11-12 11:52 ` 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=472EEF5E.2060308@ecoscentric.com \
--to=jld@ecoscentric.com \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=ecos@xylanta.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).