From: Sam Ravnborg <sam@ravnborg.org>
To: Romain Lievin <rlievin@free.fr>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: kconfig (gkc): GTK tool released, please test again...
Date: Tue, 26 Nov 2002 21:49:32 +0100 [thread overview]
Message-ID: <20021126204932.GA14147@mars.ravnborg.org> (raw)
In-Reply-To: <20021126202448.GA4072@free.fr>
On Tue, Nov 26, 2002 at 09:24:48PM +0100, Romain Lievin wrote:
> Hi,
>
> I converted gkc to GTK+ 2.0 and improved/fixed it according to your
> suggestions.
> I submit it again for testing... You will find it at
> <http://tilp.info/perso/gkc.html>.
Could you add a patch as well, that makes it much easier to try out.
No matter it is big, it's still more convinient.
Sam
next prev parent reply other threads:[~2002-11-26 20:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-10 13:27 kconfig (gconf): GTK tool released, please test Romain Lievin
2002-11-10 14:55 ` Roman Zippel
2002-11-26 20:24 ` kconfig (gkc): GTK tool released, please test again Romain Lievin
2002-11-26 20:49 ` Sam Ravnborg [this message]
[not found] ` <20021128091059.GB388@free.fr>
[not found] ` <Pine.LNX.4.44.0211281204030.2113-100000@serv>
[not found] ` <20021128141223.GA601@free.fr>
[not found] ` <Pine.LNX.4.44.0211282111110.2113-100000@serv>
[not found] ` <20021128221239.GA1305@free.fr>
[not found] ` <Pine.LNX.4.44.0211282318590.2113-100000@serv>
2002-11-29 21:48 ` kconfig (gkc): patch & help about Makefile Romain Lievin
2002-11-29 22:25 ` Sam Ravnborg
2002-11-29 21:59 ` Romain Lievin
2002-12-12 21:29 ` kconfig (gkc) [PATCH] Romain Lievin
2002-12-12 22:27 ` Roman Zippel
[not found] ` <20021219195224.GC1037@free.fr>
[not found] ` <3E04E30D.B2947D61@linux-m68k.org>
[not found] ` <20021222174307.GB24289@free.fr>
[not found] ` <3E1441B5.AB9A55C3@linux-m68k.org>
2003-01-12 11:00 ` Romain Lievin
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=20021126204932.GA14147@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rlievin@free.fr \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®