4 ms·
Here's the change and it's justification: http://git.savannah.gnu.org/cgit/grep.git/commit/?id=c6e3ea61d9f08aa0128a0eb13d31a2fbad376f99 http://git.savannah.gnu
by js2 14y ago
Here's the change and it's justification:
http://git.savannah.gnu.org/cgit/grep.git/commit/?id=c6e3ea61d9f08aa0128a0eb13d31a2fbad376f99 http://git.savannah.gnu.org/cgit/grep.git/commit/?id=c6e3ea6...
Change -r to follow only command-line symlinks, and by default to read only devices named on the command line. This is a simple way to get a more-useful behavior when searching random directories; the idea is to use 'find' if you want something fancy. -R acts as before and gets a new alias --dereference-recursive.
Personally I think breaking compatibility for this change was a poor decision.
- akkartik 14y agoThat link doesn't work. I thought at first that it was incorrectly copied, but you can see it here: http://git.savannah.gnu.org/cgit/grep.git/log/?qt=grep&q=Change+-r http://git.savannah.gnu.org/cgit/grep.git/log/?qt=grep&q... And clicking on it says 'No repositories found'. Anybody else have this problem?
- cschramm 14y agoYes, seems like Savannah can't completely handle HN ;)
- akkartik 14y agoThe error message doesn't suggest this is a load issue. Also, wouldn't the entire app go down rather than a single link?
- cschramm 14y agoIf it's not a load issue and neither some intended limitation to prevent load issues, somebody pulled it on purpose. ...which I actually included in not being able to handle HN. ;)
- js2 14y agoAlternate link: http://repo.or.cz/w/grep.git/commit/c6e3ea61d9f08aa0128a0eb13d31a2fbad376f99 http://repo.or.cz/w/grep.git/commit/c6e3ea61d9f08aa0128a0eb1... (Yea for the "D" in DVCS.) Also, the corresponding bug which has additional discussion: http://savannah.gnu.org/bugs/?17623 http://savannah.gnu.org/bugs/?17623
- cschramm 14y agoThe commit details are back now. :)
- a3_nm 14y agoRelevant thread on the ML: https://lists.gnu.org/archive/html/bug-grep/2012-03/msg00028.html https://lists.gnu.org/archive/html/bug-grep/2012-03/msg00028...
- morsch 14y agothe idea is to use 'find' if you want something fancy I don't get it, can someone explain? It also appears in the ML thread linked elsewhere, and I don't understand it there either. (I understand the reasons for the change in behaviour, just not this specific line.)
- bluetech 14y agofind is essentially the command line tool for traversing the file system hierarchy recursively. It's got a million options, e.g. whether to follow symlinks, depth, file/directory/device/.., user, group, change time and many more. When you use grep -r, it only does the most common thing which is to just go over all the files. If you want something more "fancy", you can use find, e.g.: $ find -name '*.c' -type f -exec grep printf '{}' +
- lexarchy 14y agoit's justification s/it's/its/ The same goes for the OP, BTW: This change is definitely a problem, as you say, but I think Debian going it's own way makes it even worse. He means "going its own way", of course.