All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: 822369@bugs.debian.org
Subject: Bug#822369: fixed in qemu 1:2.6+dfsg-1
Date: Thu, 19 May 2016 17:48:05 +0300	[thread overview]
Message-ID: <573DD225.5040502@msgid.tls.msk.ru> (raw)
In-Reply-To: <573DCFAA.8000500@physik.fu-berlin.de>

19.05.2016 17:37, John Paul Adrian Glaubitz пишет:
> Control: reopen -1
> 
> Hi Michael!
> 
> You closed a bug in src:xfsprogs with a new version of qemu, I don't
> think this is correct and this bug should therefore be reopened.
> 
> While qemu doesn't seem to be affected by this particular issue anymore,
> I don't think the bug in src:xfsprogs itself has been fixed since there
> hasn't been a new upload of xfsprogs since February.
> 
> Please be more careful when handling of bug reports!

Actually it is more interesting.  This bug is listed in qemu bug list,
see https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=qemu , AND in
xfsprogs bug list, see
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=xfsprogs

I closed it thinking it is in qemu.  But I closed it wrongly anyway,
and that's where I should've been more careful.  In qemu there was
a workaround proposed for this issue, but it hasn't been applied,
and I thought it has been.  So it has already been reopened meanwhile.

How it is present in both qemu and xfsprogs bug lists, I've no idea :)

/mjt

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2016-05-19 14:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-19 14:37 Bug#822369: fixed in qemu 1:2.6+dfsg-1 John Paul Adrian Glaubitz
2016-05-19 14:48 ` Michael Tokarev [this message]
2016-05-19 14:55   ` John Paul Adrian Glaubitz
2016-05-19 15:07     ` Michael Tokarev
2016-05-29 10:48       ` James Clarke

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=573DD225.5040502@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=822369@bugs.debian.org \
    --cc=glaubitz@physik.fu-berlin.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.