=== cpaelzer_ is now known as cpaelzer [17:36] for whoever knows perl here, is this "idiomatic" perl regexp? /^processor[\s\d]*:/ [17:36] or perhaps /^processor\s*\d*\s*:/ [17:36] I need to match ^processor : 0 [17:37] and ^processor 0 : stuff [17:37] cases [18:00] ahasenack: `/^processor\s+:?\s*\d+/` maybe? [18:01] looks more complicated [18:03] depends on what you want to match on. The first regex won't match the digit on the `processor : 0` variant [18:04] here's what I'm testing with: `echo -e 'processor : 0\nprocessor 0: stuff\nprocessor 0 : stuff' | grep -P '^processor\s+:?\s*\d+'` [18:05] that first regexp wasn't already matching the digit after the : [18:05] I mean, the original one [18:05] so I'm not changing that behavior [18:12] if you don't want to change the behavior and deal with a `:` between `processor` and the digit, I'd go with: `/^processor[\s\d:]+/` [18:13] it basically requires at least one space or one digit or one `:` somewhere after `processor` [18:22] also depends on what other variants also exist but you don't want them... [18:28] they should use getconf [18:30] `getconf _NPROCESSORS_ONLN` is probably better indeed === kostkon__ is now known as kostkon === elastic_dog is now known as Guest5023 [20:36] kanashiro[m]: new git published in lunar-proposed, retry builds at will [20:45] and it failed again, wth [20:46] what failed? git? [20:46] no, something that uses git [20:47] see #ubuntu-devel [20:47] just started a conversation (with myself, so far) there [20:48] * sergiodj looks === scoobydoo_ is now known as scoobydoo === markthomas1 is now known as markthomas === kenyon_ is now known as kenyon