Your message dated Fri, 8 Feb 2008 14:14:52 +0000 with message-id <[EMAIL PROTECTED]> and subject line Bug#447209: invisible dashes in gitk has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: gitk Version: 1:1.5.3.4-1 Severity: normal In the attached screenshot, gitk displays "mr -c" as "mr c". This is only a display problem. If I copy and paste the text, the dash is there. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gitk depends on: ii git-core 1:1.5.3.4-1 fast, scalable, distributed revisi ii tk8.4 8.4.16-1 Tk toolkit for Tcl and X11, v8.4 - Versions of packages gitk recommends: ii git-doc 1:1.5.3.4-1 fast, scalable, distributed revisi -- no debconf information -- see shy jo<<attachment: screenshot.png>>
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---On Wed, Feb 06, 2008 at 01:45:29PM -0500, Joey Hess wrote: > Gerrit Pape wrote: > > Hi Joey, as long as I'm not able to reproduce this, I don't know what to > > do about this bug report other than asking you to try again with a newer > > version, maybe it's fixed automagically. > > > > git 1.5.4 is available in unstable now, would you mind checking whether > > the problem still exists ;)? > > My laptop is running 1.5.4. It has also suffered a disk crash and > reinstall from scratch since I reported this bug. I can't seem to > reproduce the bug now. Ok, I close the bug for now then, if it happens to you again, feel free to re-open. Thanks, Gerrit.
--- End Message ---
