Closed GoogleCodeExporter closed 8 years ago
Please move this discussion to the macfuse-devel mailing list, unless this
turns out to be a bug in MacFUSE.
Here's my reply to your questions:
http://groups.google.com/group/macfuse-devel/browse_thread/thread/8ddca0a74765f2
00
Original comment by si...@gmail.com
on 9 May 2007 at 4:01
This MacFUSE issue-175 echoed/translated to MacFusion issue
<http://code.google.com/p/macfusion/issues/detail?id=71>
Highlight:
<http://code.google.com/p/macfusion/wiki/quick>
For as long as people omit to state version numbers and other information that
is essential for quick fixes, I'll
mark such issues in the MacFusion project area as fixed:
* in the absence of version numbers, we can assume that use of
compatible versions of MacFUSE and MacFusion
will resolve the user's issue
* regarding MacFusion checking of the MacFUSE version, we have
MacFusion issue 69 (initially critical, awaiting review by Michael)
<http://code.google.com/p/macfusion/issues/detail?id=69>
* IF a subsequent statement of version numbers suggests that an
issue _does_ exist then we at MacFusion SHOULD re-open that issue.
(Note to self: I, too, should get into the habit of stating version numbers.
It's fine for me while I'm so closely
involved with the MacFusion wiki etc, but as time passes it may become
frustrating for other viewers of issues
to note the vagueness of some reports.)
Kind regards
Graham
Original comment by grahampe...@gmail.com
on 12 May 2007 at 9:19
OT, please Ignore the hyperlink from this comment and from the previous comment
to issue 69.
I realised that a hyphenated issue would automatically present as a hyperlink,
but other markup for issues is a
mystery to me. My apologies. My plea for an explanation of markup is expressed
at
<http://code.google.com/p/support/issues/detail?id=223>.
(Wiki markup I'm OK with; it's the issue markup that's a mystery.)
Original comment by grahampe...@gmail.com
on 12 May 2007 at 9:24
I don't have access to your type of FTP server, but defer_auth should take care
of this issue, otherwise curlftpfs
might have to be extended.
Original comment by si...@gmail.com
on 26 Jun 2007 at 8:30
Original issue reported on code.google.com by
timmons....@gmail.com
on 9 May 2007 at 2:51