On Fri, 27 Jan 2006, Leonard den Ottolander wrote:
Roland, I'll revert your patch if you don't mind.
To avoid this in the future, please, give a patch some time and discuss it
first on the devel list.
___
Mc-devel mailing list
Follow-up Comment #5, bug #4327 (project mc):
The third paragraph in comment #4 is a incorrect combination of 2 thoughts.
What I meant to say is:
1) We can't determinate whether the date string is 3 or 4 fields long if the
file name contains spaces so we need to fix our input
Leonard den Ottolander wrote:
Follow-up Comment #5, bug #4327 (project mc):
The third paragraph in comment #4 is a incorrect combination of 2 thoughts.
What I meant to say is:
1) We can't determinate whether the date string is 3 or 4 fields long if the
file name contains spaces so we need to
Hi Pavel,
On Sat, 2006-01-28 at 10:34 +0200, Pavel Tsekov wrote:
To avoid this in the future, please, give a patch some time and discuss it
first on the devel list.
Yes, that would have been best, but this issue and it's ins and outs
have been discussed months ago and only Roland joined the
Hi Roland,
On Sat, 2006-01-28 at 14:58 +0100, Roland Illig wrote:
Just another idea: We could use the NLST command to only list the names
of the files and later check for them in the LIST command. This would
make it possible to deal with all but filenames containing \r\n.
This task is
Follow-up Comment #3, bug #4327 (project mc):
The current development version has the valid range of years restricted to
1970 .. 2015.
___
Reply to this item at:
http://savannah.gnu.org/bugs/?func=detailitemitem_id=4327
Update of bug #4327 (project mc):
Status: Postponed = Fixed
Assigned to: sav = leonardjo
Open/Closed:Open = Closed
Follow-up Comment #2, bug #4327 (project mc):
The problem is the code looks for entries like Mon DD hh:mm (ctime) or
Mon DD hh:mm.
Are there any places where a ctime is passed to vfs_parse_filedate()? If so
maybe we should fix the string before passing it to vfs_parse_filedate()? Or
