Time to merge in_tail_ex and in_tail_multiline features into in_tail?

[repeatedly]

From our experiences, some Fluentd users use in_tail_ex or in_tail_multiline instead of in_tail.
And for advanced use-case, some users want more rich in_tail plugin which has in_tail_ex and in_tail_multiline combination.

I think providing these features in in_tail is better for Fluentd users.
What do you think?

@yosisa
@tomohisaota

[tomohisaota]

I love that idea 👍

[wsorenson]

As I requested this on the mailing list, a big 👍 from me.

[repeatedly]

@yosisa Do you have any concern?
I will finish in_tail_multiline merge soon.
After that, I want to merge in_tail_ex features into in_tail.

[yosisa]

I also agree with you, It's nice idea!

[repeatedly]

Okay. I just merged the pull request that supports in_tail_multiline feature.
Next step is in_tail_ex merge.

[graysky]

@repeatedly are you actively working on the in_tail_ex merge? If not, I may be able to help. It is a feature we would benefit from having.

[repeatedly]

@graysky Yes. I will pull request it after tomorrow lecture.
And I have a plan for releasing fluentd 0.10.45 in this week.

[repeatedly]

@graysky I just did pull request. Could you check the code and test the your environment?

[graysky]

@repeatedly Awesome. Sure, I'll try this out today

[repeatedly]

Just merged two pull requests.