From: foser <foser@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] GTK und GTK2 Use Flag
Date: Tue, 29 Mar 2005 23:35:50 +0200 [thread overview]
Message-ID: <1112132150.13737.9.camel@rivendell> (raw)
In-Reply-To: <1112116825.23696.46.camel@powerix.local.c0ffeine.de>
[-- Attachment #1: Type: text/plain, Size: 413 bytes --]
On Tue, 2005-03-29 at 19:20 +0200, Markus Nigbur wrote:
<snip much gtk2 use flag blah and old ideas>
The gtk2 flag is meant to be removed in time, not to be promoted even
more -than it was ever meant to be- as it is.
Do it right this time this time, don't try to redo it in as much a
crappy way as it is now. The proposals here are as much time-context
dependant as the current solution is.
- foser
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-29 21:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 10:15 [gentoo-dev] GTK und GTK2 Use Flag Fabian Zeindl
2005-03-29 10:58 ` Stefan Sperling
2005-03-29 11:04 ` Diego "Flameeyes" Pettenò
2005-03-29 11:11 ` Stefan Sperling
2005-03-29 11:24 ` Diego "Flameeyes" Pettenò
2005-03-29 11:35 ` David Morgan
2005-03-29 11:50 ` Brian Harring
2005-03-29 13:09 ` David Morgan
2005-03-29 13:39 ` Brian Harring
2005-03-29 14:19 ` David Morgan
2005-03-29 15:38 ` Stefan Sperling
2005-03-29 17:20 ` Markus Nigbur
2005-03-29 21:35 ` foser [this message]
2005-03-29 21:42 ` Ciaran McCreesh
2005-03-30 9:00 ` Paul de Vrieze
2005-03-29 22:29 ` Brian Harring
2005-03-29 22:46 ` Ciaran McCreesh
2005-03-29 23:09 ` Olivier Crête
2005-03-29 23:13 ` foser
2005-03-29 23:33 ` Brian Harring
2005-03-30 4:32 ` Dulmandakh Sukhbaatar
2005-03-30 8:44 ` Diego "Flameeyes" Pettenò
2005-03-29 11:05 ` Stefan Sperling
2005-03-29 11:11 ` Brian Harring
2005-03-29 20:49 ` Spider
2005-03-29 22:43 ` Brian Harring
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=1112132150.13737.9.camel@rivendell \
--to=foser@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.gentoo.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