util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Naja Melan <najamelan@autistici.org>
Cc: util-linux@vger.kernel.org
Subject: Re: umount failing on paths which end in a backslash
Date: Mon, 13 Aug 2012 16:42:04 +0200	[thread overview]
Message-ID: <20120813144204.GF21956@x2.net.home> (raw)
In-Reply-To: <20120810234435.6af1f6d1@localhost>

On Fri, Aug 10, 2012 at 11:44:35PM +0200, Naja Melan wrote:
> I tried to report this bug months ago to the debian maintainers of
> mount, but debian bug reporting is a minefield and by email all I
> got was a lousy answer from someone who didn't understand escaping
> in bash strings and who obviously never ran the script demonstrating
> the issue.

 Fixed. It seems like a pretty old bug (v2.19 or so...). Thanks!

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

      reply	other threads:[~2012-08-13 14:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-10 21:44 umount failing on paths which end in a backslash Naja Melan
2012-08-13 14:42 ` Karel Zak [this message]

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=20120813144204.GF21956@x2.net.home \
    --to=kzak@redhat.com \
    --cc=najamelan@autistici.org \
    --cc=util-linux@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).