Junio C Hamano wrote:I don't see the advantage of doing it that way. After all, we're pattern matching. Does using a hash, an array, and a call to map() gain us something? I think a regular expression is clearer. Of course, as Jeff pointed out, I should have used a whitespace-agnostic regular expression. + elsif ($word =~ /black|red|green|yellow| + blue|magenta|cyan|white/x ) { I agreed with the rest of your suggestions, and will implement them in the next round of changes, later this week. Dan - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| jjohansen | [AppArmor 39/45] AppArmor: Profile loading and manipulation, pathname matching |
| Vladislav Bolkhovitin | Re: Integration of SCST in the mainstream Linux kernel |
| Heiko Carstens | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Andrew Morton | 2.6.23-rc6-mm1 |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Evgeniy Polyakov | Re: [BUG] New Kernel Bugs |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
