From: "Tobias J. Schwinger" <schwinger@klest.de>
To: "foser" <foser@foser.dyn.warande.net>
Cc: <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] typo in sawfish-2.0 source
Date: Tue, 3 Jun 2003 15:19:48 +0200 [thread overview]
Message-ID: <011c01c329d2$d4165450$1b2a10ac@victoria> (raw)
In-Reply-To: 1054590273.8196.9.camel@rivendell
[-- Attachment #1: Type: text/plain, Size: 594 bytes --]
----- Original Message -----
From: "foser" <foser@foser.dyn.warande.net>
To: <gentoo-dev@gentoo.org>
Sent: 02 June, 2003 23:44
Subject: Re: [gentoo-dev] typo in sawfish-2.0 source
> The check was ok around the time sawfish-2.0 was released around the
> time gtk+-2.0 hit the streets, but isn't correct anymore with gtk+-2.2
> in the tree. Your check isn't completely correct either, cause sawfish
> will work with gtk+-2.0 just fine (it checks the minor version no.).
OH ! I REALIZE THAT WAS STUPID - I'M SORRY I DIDN'T WANT TO CONFUSE ANYONE.
thanx for pointing it out.
[-- Attachment #2: Type: text/html, Size: 1687 bytes --]
prev parent reply other threads:[~2003-06-03 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 18:31 [gentoo-dev] typo in sawfish-2.0 source Tobias J. Schwinger
2003-06-02 21:44 ` foser
2003-06-03 13:19 ` Tobias J. Schwinger [this message]
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='011c01c329d2$d4165450$1b2a10ac@victoria' \
--to=schwinger@klest.de \
--cc=foser@foser.dyn.warande.net \
--cc=gentoo-dev@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