llvm dev - Feb 2020 - MLIR changes not sent to any mailing lists?

On Thu, Jan 30, 2020 at 9:50 AM Tom Stellard <tstellar at redhat.com>
wrote:
>
> On 01/30/2020 05:25 AM, Hans Wennborg via llvm-dev wrote:
> > 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.
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.

On Thu, Jan 30, 2020 at 4:04 PM Hans Wennborg <hans at chromium.org>
wrote:
>
> On Thu, Jan 30, 2020 at 9:50 AM Tom Stellard <tstellar at redhat.com>
wrote:
> >
> > On 01/30/2020 05:25 AM, Hans Wennborg via llvm-dev wrote:
> > > 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.
>
> 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?

On Thu, Feb 6, 2020 at 11:24 AM Hans Wennborg <hans at chromium.org>
wrote:
>
> On Thu, Jan 30, 2020 at 4:04 PM Hans Wennborg <hans at chromium.org>
wrote:
> >
> > On Thu, Jan 30, 2020 at 9:50 AM Tom Stellard <tstellar at
redhat.com> wrote:
> > >
> > > On 01/30/2020 05:25 AM, Hans Wennborg via llvm-dev wrote:
> > > > 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.
> >
> > 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

On Thu, Feb 6, 2020 at 2:24 AM Hans Wennborg via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> On Thu, Jan 30, 2020 at 4:04 PM Hans Wennborg <hans at chromium.org>
wrote:
> >
> > On Thu, Jan 30, 2020 at 9:50 AM Tom Stellard <tstellar at
redhat.com>
> wrote:
> > >
> > > On 01/30/2020 05:25 AM, Hans Wennborg via llvm-dev wrote:
> > > > 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.
> >
> > 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?
>
http://lists.llvm.org/pipermail/all-commits/Week-of-Mon-20200203/007991.html

-- 
Mehdi
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200206/ac5e0f6b/attachment.html>