All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Debian Bug Tracking System" <owner@bugs.debian.org>
To: Niels Thykier <niels@thykier.net>
Cc: linux-xfs@vger.kernel.org, debian-bugs-closed@lists.debian.org
Subject: Processed: closing 793495
Date: Sun, 10 Feb 2019 20:03:05 +0000	[thread overview]
Message-ID: <handler.s.C.154982891825038.transcript@bugs.debian.org> (raw)
In-Reply-To: 1549828897-642-bts-niels@thykier.net

Processing commands for control@bugs.debian.org:

> # Appears to be fixed but missing a done
> close 793495
Bug #793495 [xfsprogs] CVE-2012-2150 xfsprogs: xfs_metadump information disclosure
Bug #793496 [xfsprogs] xfsprogs: CVE-2012-2150: xfs_metadump information disclosure flaw
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
793495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793495
793496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793496
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

           reply	other threads:[~2019-02-10 20:03 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1549828897-642-bts-niels@thykier.net>]

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=handler.s.C.154982891825038.transcript@bugs.debian.org \
    --to=owner@bugs.debian.org \
    --cc=debian-bugs-closed@lists.debian.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=niels@thykier.net \
    /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.