Skip to content

Conversation

dgouyette
Copy link

No description provided.

@colinsurprenant colinsurprenant added this to the v1.4.2 milestone May 15, 2014
@colinsurprenant
Copy link
Contributor

for the record, this is a replacement PR for #1321 which was closed as dupliate.

@colinsurprenant
Copy link
Contributor

Looks good. I'd like a second opinion on the actual regexp, @jordansissel ? basically, my reserve is that there are far more valid timezone still not covered in this regexp - how important is it to actually match on valid tokens instead of simply matching on 3-4 chars? then the question becomes, what are the chances of having a date with an invalid timezone code?

@jordansissel jordansissel modified the milestones: 1.4.3, v1.4.2 Jun 17, 2014
@elasticsearch-release
Copy link

Can one of the admins verify this patch?

@jordansissel jordansissel modified the milestones: 1.4.3, v1.5.0 Nov 4, 2014
@jsvd
Copy link
Member

jsvd commented Nov 21, 2014

@dgouyette since we're moving the plugins to separate repositories, would you mind reopening this PR in https://github.com/logstash-plugins/logstash-filter-grok? Thanks!

@jsvd
Copy link
Member

jsvd commented Mar 9, 2015

migrated issue to logstash-plugins/logstash-patterns-core#16

@jsvd jsvd closed this Mar 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants