Re: flashkard bug

To: Jan Ulrich Hasecke <janulrich.hasecke@t-online.de>
Cc: debian-kde@lists.debian.org
Subject: Re: flashkard bug
From: Ben Burton <bab@debian.org>
Date: Tue, 8 Jul 2003 14:18:52 +1000
Message-id: <[🔎] 20030708141852.A31844@digican.ms.unimelb.edu.au>
In-reply-to: <[🔎] 87d6gmka5q.fsf@molly.hasecke>; from janulrich.hasecke@t-online.de on Mon, Jul 07, 2003 at 10:34:25AM +0200
References: <[🔎] 87ptkmkfxl.fsf@molly.hasecke> <[🔎] 200307071012.12740.suy21@lycos.es> <[🔎] 87d6gmka5q.fsf@molly.hasecke>

> I understand. But in unstable the bug seems to be fixed and the
> package is called 3.1.2-1. 

The 3.1.2 package in unstable was actually pulled from CVS
(KDE_3_1_BRANCH) shortly after KDE 3.1.2 was tagged.  So it is possible
that the bug was fixed in the brief period after CVS was tagged but
before I did the CVS pull.

Ben (flashkard maintainer).

Reply to:

References:
- flashkard bug
  - From: Jan Ulrich Hasecke <janulrich.hasecke@t-online.de>
- Re: flashkard bug
  - From: Alex <suy21@lycos.es>
- Re: flashkard bug
  - From: Jan Ulrich Hasecke <janulrich.hasecke@t-online.de>

Prev by Date: Changing kdeprint options per job
Next by Date: How to shutdown KDE from command line?
Previous by thread: Re: flashkard bug
Next by thread: Compiling KDE progs does not work
Index(es):
- Date
- Thread