Re: Possible bug in "Enable write-mode for persistency related devices in readonly/forensic mode"

To: intrigeri <intrigeri+debian-live@boum.org>
Cc: Michael Prokop <mika@grml.org>, debian-live@lists.debian.org
Subject: Re: Possible bug in "Enable write-mode for persistency related devices in readonly/forensic mode"
From: Evgeni Golov <evgeni@grml.org>
Date: Fri, 1 Jan 2016 15:53:30 +0100
Message-id: <[🔎] 20160101145330.GA16842@nana.kerker.die-welt.net>
In-reply-to: <[🔎] 8537uhtypy.fsf@boum.org>
References: <85k2nuv4sx.fsf@boum.org> <2015-12-31T21-55-29@devnull.michael-prokop.at> <[🔎] 8537uhtypy.fsf@boum.org>

Hey,

On Fri, Jan 01, 2016 at 10:50:49AM +0100, intrigeri wrote:

> Michael Prokop wrote (31 Dec 2015 20:58:15 GMT) :
> > The grep options should have been '-qw' instead AFAICT.

Indeed, fixed in Git, thanks!

> JFTR, I'm not sure what's the preferred workflow to make sure this is
> well tracked and fixed before next upload: given the buggy code only
> lives in Git and was never uploaded to Debian, I guess that a bug in
> the BTS is not appropriate.

I'd probably just fill a bug with "<last-release>+git" or something as version.
But this is not needed here anymore :)

Greets

Reply to:

Follow-Ups:
- Re: Possible bug in "Enable write-mode for persistency related devices in readonly/forensic mode"
  - From: intrigeri <intrigeri+debian-live@boum.org>

References:
- Re: Possible bug in "Enable write-mode for persistency related devices in readonly/forensic mode"
  - From: intrigeri <intrigeri+debian-live@boum.org>

Prev by Date: Re: Possible bug in "Enable write-mode for persistency related devices in readonly/forensic mode"
Next by Date: Re: Possible bug in "Enable write-mode for persistency related devices in readonly/forensic mode"
Previous by thread: Re: Possible bug in "Enable write-mode for persistency related devices in readonly/forensic mode"
Next by thread: Re: Possible bug in "Enable write-mode for persistency related devices in readonly/forensic mode"
Index(es):
- Date
- Thread