I'm setting this to Invalid again, since it's not a bug and is not going
to be changed in the future versions of mc. If you believe that it
should have been dealt with differently, feel free to act upon, but I
think at this point it doesn't matter anymore.
** Changed in: mc (Ubuntu)
P.S. I wonder why I'm not allowed to set it to wontfix, which suits it
better.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954103
Title:
Ubuntu precise, since the upgrade cd /#sh:servername no
Hi,
It's not a regression. Upstream has reworked the VFS addressing scheme,
see
$ man mc
for details, e.g. you should now use:
$ cd sh://user@machine:options/remote-dir
Z.
** Changed in: mc (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are
So how exactly did that change in Ubuntu after Feature Freeze without an
exception then?
That's a clear change of behaviour that I don't remember seeing
documented in an exception.
** Changed in: mc (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a
This is not a question that I can answer, since I was not involved in
this business, but only happen to know that the correct way of doing
what you are trying to achieve is as I described above.
Either way, it's not a bug, but rather something that upstream has been
working on for long time and
** Changed in: mc (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954103
Title:
Ubuntu precise, since the upgrade cd /#sh:servername no longer works
To
