Hi Thomas,
On Saturday 14 February 2004 11:17, Thomas Heidemann wrote:
> I reported this bug to one of the SuSE guys who talked to one of the
> QT programmers. This Bug (in QString) is fixed now in the current QT
> version.
>
> So there is no need to apply the patch _if_ you use an up-to-date qt
Hello Thomas Heidemann,
On Sat, 14 Feb 2004 11:42:36 +0100 Thomas Heidemann <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On Saturday 14 February 2004 11:27, wwp wrote:
> > Hello Thomas,
> [...]
> > >
> > > I reported this bug to one of the SuSE guys who talked to one of
> > > the QT programmers. This B
Hi,
On Saturday 14 February 2004 11:27, wwp wrote:
> Hello Thomas,
[...]
> >
> > I reported this bug to one of the SuSE guys who talked to one of
> > the QT programmers. This Bug (in QString) is fixed now in the
> > current QT version.
> >
> > So there is no need to apply the patch _if_ you use an
Hello Thomas,
On Sat, 14 Feb 2004 11:17:26 +0100 Thomas Heidemann <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On Friday 13 February 2004 22:30, Thomas Reitelbach wrote:
> [...]
> > Thank you very much for your contribution, i put a link to this patch
> > on the licq website (download-section).
>
> I
Hi,
On Friday 13 February 2004 22:30, Thomas Reitelbach wrote:
[...]
> Thank you very much for your contribution, i put a link to this patch
> on the licq website (download-section).
I reported this bug to one of the SuSE guys who talked to one of the QT
programmers. This Bug (in QString) is fix
