On Sat, May 02, 2009 at 09:33:57PM +0100, Adam D. Barratt wrote: > >From what I remember, the rationale behind the "only one file" behaviour > was that it allowed to say "what is the license of this file", even if > that single file did not match the default set of files which are > checked.
Makes sense. My beef is that it suddenly goes away when I ask "what is the license of these two files". > This might be losing something in translation. :-) Given that > licensecheck is a command line tool, how can those options /not/ "be > applied to the command line"? I should've specified: for each non-directory command line argument. I would draw a parallel with ls(1): if I type "ls" or "ls <dir>", I expect that some entries in <dir> will be ignored by default. However, if I explicitly ask "ls .bashrc", I now expect that file to be listed, with or without "-a". IOW, it's line 261 that I'm against, not line 256. :) -- <liiwi> udp - universal dropping of an pigeon -- To unsubscribe, send mail to [email protected].
