MLIR changes not sent to any mailing lists?

For example, 7984b47401f7f36475619abf2ff02de3b5ff0481 does not seem to
have made it to any mailing lists.

This makes things harder for me as release manager, as those changes
are essentially landing under the radar.

Can we please make sure all commits that get pushed upstream are sent
to a -commits list?

Who is the right person to ask about this?

Thanks,
Hans

For example, 7984b47401f7f36475619abf2ff02de3b5ff0481 does not seem to
have made it to any mailing lists.

This makes things harder for me as release manager, as those changes
are essentially landing under the radar.

Can we please make sure all commits that get pushed upstream are sent
to a -commits list?

Who is the right person to ask about this?

I'm looking into this.

If you want to guarantee that you get every email. I suggest you
subscribe to https://lists.llvm.org/cgi-bin/mailman/listinfo/all-commits
which gets all the commit emails directly from github.

-Tom

I actually tried subscribing to that but it didn't work; maybe my
subscription request got stuck in moderation?

It's also sub-optimal because it would duplicate all the emails
already getting sent to the regular -commits lists, but I'd rather
have too much email than too little.

Here's another one that passed under my radar:
31fd112eb4a90600e0f340f19053e5715e92ec4c

Any progress on getting these sent to llvm-commits or some other list?

Here's a non-MLIR commit that also wasn't sent to any list:
b3576f60ebc8f660afad8120a72473be47517573

http://lists.llvm.org/pipermail/all-commits/Week-of-Mon-20200203/007991.html

Here’s a non-MLIR commit that also wasn’t sent to any list:
b3576f60ebc8f660afad8120a72473be47517573

I don’t think that this is the same issue as the mlir commits. This particular one is likely due to the issue of non-ascii characters the commit summary (author/comitter name in this case) causing some sort of failure somewhere in the email pipeline, resulting in emails not turning up on the list:
http://lists.llvm.org/pipermail/llvm-dev/2019-August/134516.html
http://lists.llvm.org/pipermail/llvm-dev/2019-November/137292.html
http://lists.llvm.org/pipermail/llvm-dev/2019-December/137508.html

My guess is that somewhere on some server involved in sending the emails there’s a series of error messages hiding in a logfile about invalid ascii characters from some software that isn’t utf-8 aware. I don’t know who owns that process though.

-Greg

    Here's a non-MLIR commit that also wasn't sent to any list:
    b3576f60ebc8f660afad8120a72473be47517573

I don't think that this is the same issue as the mlir commits. This particular one is likely due to the issue of non-ascii characters the commit summary (author/comitter name in this case) causing some sort of failure somewhere in the email pipeline, resulting in emails not turning up on the list:
http://lists.llvm.org/pipermail/llvm-dev/2019-August/134516.html
http://lists.llvm.org/pipermail/llvm-dev/2019-November/137292.html
http://lists.llvm.org/pipermail/llvm-dev/2019-December/137508.html
My guess is that somewhere on some server involved in sending the emails there's a series of error messages hiding in a logfile about invalid ascii characters from some software that isn't utf-8 aware. I don't know who owns that process though.

You are correct, this second email is the same non-ascii issue. I
think we have a fix now and hopefully we'll be able to deploy it soon.

-Tom

Nice. Thanks Tom!

Yes, all-commits does seem to get all commits which is great, except
that I haven't been able to subscribe to it.

The "Subscription results" page says "Depending on the configuration
of this mailing list, your subscription request may have to be first
confirmed by you via email, or approved by the list moderator."

I never received any confirmation email. Tom seems to be a moderator
for this, so maybe he can help?

That's great, thanks!

Looks like this works now - now I saw the first mail for a commit from myself since the transition to git. Thanks!

// Martin

    Here's a non-MLIR commit that also wasn't sent to any list:
    b3576f60ebc8f660afad8120a72473be47517573

I don't think that this is the same issue as the mlir commits. This particular one is likely due to the issue of non-ascii characters the commit summary (author/comitter name in this case) causing some sort of failure somewhere in the email pipeline, resulting in emails not turning up on the list:
http://lists.llvm.org/pipermail/llvm-dev/2019-August/134516.html http://lists.llvm.org/pipermail/llvm-dev/2019-November/137292.html http://lists.llvm.org/pipermail/llvm-dev/2019-December/137508.html My guess is that somewhere on some server involved in sending the emails there's a series of error messages hiding in a logfile about invalid ascii characters from some software that isn't utf-8 aware. I don't know who owns that process though.

You are correct, this second email is the same non-ascii issue. I
think we have a fix now and hopefully we'll be able to deploy it soon.

Looks like this works now - now I saw the first mail for a commit from myself since the transition to git. Thanks!

Yes, the utf-8 issue has been fixed, and there is now an mlir-commits list.

-Tom

Want to update the llvm.org page with links to the MLIR commits list?

Excellent! Many thanks!

Do you mean the mailing list links in the left-hand column? It doesn't
have links to cfe-commits etc. either. I've added a "more" link to all
the mailing lists there.