On Nov 5, 2010, at 9:58 AM, Junio C Hamano wrote: > Nguyán ThÃi Ngác Duy <pclouds@xxxxxxxxx> writes: > >> Full pattern must be quoted. So 'pat"t"ern attr' will give exactly >> 'pat"t"ern', not 'pattern'. Also clarify that leading whitespaces are >> not part of the pattern and document comment syntax. >> >> Signed-off-by: Nguyán ThÃi Ngác Duy <pclouds@xxxxxxxxx> >> --- >> Obvious regression: patterns that begin with double quote will >> now work differently. > > I'm really hesitant to pursue this route and break people's existing > setups, especially if the only benefit this patch tries to achieve is to > allow somebody to say: > > "Program Files/*.txt" ...some attr... > > It is not worth the effort, risk and headache, especially because people > with such paths are probably already using > > Program?Files/*.txt ...some attr.. > > to match them. Would this actually break any existing setups? The only ones that are affected are ones beginning with ", which I imagine would be rather rare. I personally am in favor of having an unambiguous way to encode whitespace into the pattern. Having to use ? has always struck me as being, well, not very good, especially if you have 2 files that only differ at that character (e.g. file.1 and "file 1"). -Kevin Ballard-- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html