This repo is obsolete, please follow `jaqx0r/mtail` instead

[jaqx0r]

No mtail maintainers have write access to this repository anymore so please repoint your git remote upstreams to https://github.com/jaqx0r/mtail and docker images to ghcr.io/jaqx0r/mtail. Documentation now hosted at https://jaqx0r.github.io/mtail

[avesst]

@jaqx0r I think more information is warranted here. Could you elaborate on what happened to this repository?

[anarcat]

it would be great to have some official word from @google / @google-admin that this is abandoned? perhaps archiving the repo and pointing to the new one is in order?

[jaqx0r]

It's not abandoned. Work continues in jaqx0r/mtail as already stated.

…

On Thu, 20 Mar 2025, 02:36 anarcat, ***@***.***> wrote: it would be great to have some official word from @google <https://github.com/google> / @google-admin <https://github.com/google-admin> that this is abandoned? perhaps archiving the repo and pointing to the new one is in order? — Reply to this email directly, view it on GitHub <#929 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXFX6ZZT4CIXJ7TD3WQV6L2VGFHDAVCNFSM6AAAAABQCXW22OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZXGA4TONRVGE> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: anarcat]*anarcat* left a comment (google/mtail#929) <#929 (comment)> it would be great to have some official word from @google <https://github.com/google> / @google-admin <https://github.com/google-admin> that this is abandoned? perhaps archiving the repo and pointing to the new one is in order? — Reply to this email directly, view it on GitHub <#929 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXFX6ZZT4CIXJ7TD3WQV6L2VGFHDAVCNFSM6AAAAABQCXW22OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZXGA4TONRVGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[anarcat]

It's not abandoned. Work continues in jaqx0r/mtail as already stated.

I understand, but you might understand why people could be a little hesitant into switching over from an official-looking @google repository to what seems at first glance like a third-party fork. I understand you're the primary maintainer here, but it would still be good, IMHO, to archive the @google repository and point to yours to make things official.

[czerasz]

A mention in README.md would be nice! IMHO this is the minimum...

Otherwise how does someone know, that @google repository is not active and work is continued on https://github.com/jaqx0r/mtail?

[chengchuanpeng]

Hi @jaqx0r ,
I recently opened a PR here and am currently waiting for someone to manually trigger the pipelines, as it's pending. In the meantime, I came across this discussion, should I instead open a PR directly to your repository?

[jaqx0r]

@chenchuanpeng Yes please.

…

On Thu, 29 May 2025, 04:05 ZenoPeng, ***@***.***> wrote: *chengchuanpeng* left a comment (google/mtail#929) <#929 (comment)> Hi @jaqx0r <https://github.com/jaqx0r> , I recently opened a PR here and am currently waiting for someone to manually trigger the pipelines, as it's pending. In the meantime, I came across this discussion, should I instead open a PR directly to your repository? — Reply to this email directly, view it on GitHub <#929 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXFX6YDHV453XBVRPWVM6D3AX3HFAVCNFSM6AAAAABQCXW22OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMJXGE4DGNBSHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>