public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Weddington, Eric" <eweddington@cso.atmel.com>
To: "Dave Korn" <dave.korn@artimi.com>,
	"Keith Seitz" <keiths@redhat.com>,
	        "insight" <insight@sourceware.org>
Subject: RE: [PATCH/libgui] Fix cygwin build woes
Date: Tue, 05 Aug 2008 17:25:00 -0000	[thread overview]
Message-ID: <258DDD1F44B6ED4AAFD4370847CF58D5023FADD0@csomb01.corp.atmel.com> (raw)
In-Reply-To: <006a01c8f71d$544a8020$9601a8c0@CAM.ARTIMI.COM>

 

> -----Original Message-----
> From: insight-owner@sourceware.org 
> [mailto:insight-owner@sourceware.org] On Behalf Of Dave Korn
> Sent: Tuesday, August 05, 2008 11:05 AM
> To: 'Keith Seitz'; 'insight'
> Subject: RE: [PATCH/libgui] Fix cygwin build woes
> 
>   Once I've got gcc4 and setup.exe under control, I'll 
> volunteer some time
> and attention toward helping with insight.
> 
>   I really quite like the look-and-feel of the current 
> insight, and the
> independence from X, and I'd be willing to take a look at the 
> tk/tcl/etc
> "hybrid monsters" with a view to modernising them (refresh relative to
> upstream sources) and making them build and run good for both 
> cygwin and
> mingw on windows, if that turns out to be possible.

You already have my thanks! :-)

  reply	other threads:[~2008-08-05 17:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-02 23:36 Keith Seitz
2008-08-04 23:35 ` Christopher Faylor
2008-08-05  4:13   ` Keith Seitz
2008-08-05 15:01     ` Christopher Faylor
2008-08-05 17:05       ` Dave Korn
2008-08-05 17:25         ` Weddington, Eric [this message]
2008-08-05 17:55           ` Dave Korn
2008-08-05 17:59             ` Weddington, Eric
2008-08-05 18:46               ` [OT] " Dave Korn
2008-08-05 20:53         ` Christopher Faylor
2008-08-06  9:28           ` Dave Korn

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=258DDD1F44B6ED4AAFD4370847CF58D5023FADD0@csomb01.corp.atmel.com \
    --to=eweddington@cso.atmel.com \
    --cc=dave.korn@artimi.com \
    --cc=insight@sourceware.org \
    --cc=keiths@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).