From: Michal Marek <mmarek@suse.cz>
To: Tiana Rakotovao Andriamahefa <rkmahefa@gmail.com>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: qt3 and ptrdiff_t build error
Date: Thu, 24 Jan 2013 11:36:31 +0100 [thread overview]
Message-ID: <51010EAF.4090704@suse.cz> (raw)
In-Reply-To: <20130116122610.GA7613@rak.local>
On 16.1.2013 13:26, Tiana Rakotovao Andriamahefa wrote:
> I have checked it and found that the error was effectively fixed in the last
> maintained upload of Qt3 in 2011. However, the correction is not yet in Wheezy
> (Debian testing) which I have used for more than a year. It might be
> included there one day!
> This is the case of Debian, but not all distros.
OK. And it is dead upstream. So I'll apply your patch. Could you please
resend it? I deleted the email already.
Thanks,
Michal
prev parent reply other threads:[~2013-01-24 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130115231251.GA6100@rak.local>
[not found] ` <20130116063156.GA28910@pryan.ekaia.org>
2013-01-16 12:26 ` qt3 and ptrdiff_t build error Tiana Rakotovao Andriamahefa
2013-01-24 10:36 ` Michal Marek [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=51010EAF.4090704@suse.cz \
--to=mmarek@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkmahefa@gmail.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 NNTP newsgroup(s).