Messages in this thread | | | Date | Sat, 9 Apr 2005 10:08:27 -0700 | From | Paul Jackson <> | Subject | Re: Kernel SCM saga.. |
| |
Linus wrote: > (you need to remember to escape '%' > too when you do that ;).
No - don't have to. Not if I don't mind giving fools that embed newlines in paths second class service.
In my case, if I create a file named "foo\nbar", then backup and restore it, I end up with a restored file named "foo%0Abar". If I had backed up another file named "foo%0Abar", and now restore it, it collides, and last one to be restored wins. If I really need the "foo\nbar" file back as originally named, I will have to dig it out by hand.
I dare say that Linux kernel source does not require first class support for newlines embedded in pathnames.
> ASCII isn't magical.
No - but it's damn convenient. Alot of tools work on line-oriented ASCII that don't work elsewhere.
I guess Perl-hackers won't care much, but those working with either classic shell script tools or Python will find line formatted ASCII more convenient.
-- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson <pj@engr.sgi.com> 1.650.933.1373, 1.925.600.0401 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |