Re: Commit messages no longer working
Raymond Toy <[email protected]> Mon, 17 Apr 2023 19:31:35 -0700
| Newsgroups | gmane.lisp.common-lisp-net.devel |
|---|---|
| Message-ID | <[email protected]> |
On 4/17/23 18:29, Jon Boone wrote: > Hi Ray, > > Here's the list of the final items which I expect you /*did*/ get > emails for the associated modifications: > > * CMUCL/CMUCL Issue 120 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/issues/120> > Yes. Well at least some of them. It will take some time to match up the comments with the emails. > > * CMUCL/CMUCL Issue 178 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/issues/178> > No. I can't find any evidence of issue 178 in my emails. > > * CMUCL/CMUCL Merge Request 128 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/merge_requests/128> > Yes. Again at least some. > > * CMUCL/CMUCL Master Commit c26f8ede5b0828a2db337fc372ab09d7b49fd5e1 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/commit/c26f8ede5b0828a2db337fc372ab09d7b49fd5e1> > Yes, I received this commit message. > > Here's the list of items that I expect you did not get emails for the > associated modifications: I did not check all of the following. But I can tell you that the last message from any issue was on Mar 24, 3:57 PM (from you actually for issue 143). > > * CMUCL/CMUCL Issue 179 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/issues/179> > Didn't get it. > > * CMUCL/CMUCL Issue 180 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/issues/180> > Didn't get it. > > * CMUCL/CMUCL Issue 181 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/issues/181> > Didn't get it. > > * CMUCL/CMUCL Issue 182 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/issues/182> > Nope. > > * CMUCL/CMUCL Task 183 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/work_items/183?iid_path=true> > * CMUCL/CMUCL Task 184 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/work_items/184?iid_path=true> > * CMUCL/CMUCL Issue 185 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/issues/185> > * CMUCL/CMUCL Issue 186 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/issues/186> > * CMUCL/CMUCL Issue 187 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/issues/187> > * CMUCL/CMUCL Merge Request 113 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/merge_requests/113> > I did get the merge message for this MR. > > * CMUCL/CMUCL Merge Request 72 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/merge_requests/72> > I don't think I got the email for the correction to the MR which was recent. The actual merge was a year ago, and that worked. > > * CMUCL/CMUCL Merge Request 135 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/merge_requests/135> > * CMUCL/CMUCL Merge Request 136 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/merge_requests/136> > * CMUCL/CMUCL Merge Request 137 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/merge_requests/137> > * CMUCL/CMUCL Merge Request 138 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/merge_requests/138> > * CMUCL/CMUCL Merge Request 139 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/merge_requests/139> > * CMUCL/CMUCL Merge Request 93 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/merge_requests/93> > * CMUCL/CMUCL Master Commit 5dc0d7bfe3120f1fc3a329219873db55c8d8b9c6 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/commit/5dc0d7bfe3120f1fc3a329219873db55c8d8b9c6> > I think I got this commit message. > > * CMUCL/CMUCL Master Commit 3578e01505f9afc9272d6575c864ef632c57e6b7 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/commit/3578e01505f9afc9272d6575c864ef632c57e6b7> > I think I got this one too. > > * CMUCL/CMUCL Master Commit ce823be49f25fee853310b27bfcdd46e6b3b8be8 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/commit/ce823be49f25fee853310b27bfcdd46e6b3b8be8> > Got it. > > * CMUCL/CMUCL Master Commit b9b145ab66b7cf2195390c4ac987f4f6566432cb > <https://gitlab.common-lisp.net/cmucl/cmucl/-/commit/b9b145ab66b7cf2195390c4ac987f4f6566432cb> > Got it. > > * CMUCL/CMUCL Master Commit 72cdab53b26e93d2e42afc7554968ed1361ef54a > <https://gitlab.common-lisp.net/cmucl/cmucl/-/commit/72cdab53b26e93d2e42afc7554968ed1361ef54a> > Got it. > > * CMUCL/CMUCL Master Commit bbfff3c049e693224fa31431ea60459a0aa752b7 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/commit/bbfff3c049e693224fa31431ea60459a0aa752b7> > Got it. This is one the newer ones where commit messages were working again. > > * CMUCL/CMUCL Master Commit 5196072ac8c7bf2c12b26ff766cfad2dbed434d7 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/commit/5196072ac8c7bf2c12b26ff766cfad2dbed434d7> > Got it. Another recent commit from a day ago. > > * CMUCL/CMUCL Master Commit b2aee0f70567e3e36579517cee771e753ada80b4 > <https://gitlab.common-lisp.net/cmucl/cmucl/-/commit/b2aee0f70567e3e36579517cee771e753ada80b4> > Got this too which is another very recent commit. > Can you please confirm? > > —jon > > > On Mon, Apr 17, 2023 at 4:09 PM Erik Huelsmann <[email protected]> wrote: > > You could, but it's not required. I'm sending there to make sure > other people with admin access to the box are up to date on it as > well. > > On Mon, Apr 17, 2023 at 9:46 PM Raymond Toy > <[email protected]> wrote: > > > On 4/17/23 12:24, Erik Huelsmann wrote: >> >> >> On Mon, Apr 17, 2023 at 5:03 PM Raymond Toy >> <[email protected]> wrote: >> >> >> On 3/29/23 13:54, Raymond Toy wrote: >> > I did some commits to cmucl today and I'm not receiving >> commit >> > messages anymore. The last commit message I see (to >> > [email protected]) was on Mar 23, a few days >> ago. I haven't >> > changed any settings that I know of. Did something on >> common-lisp.net <http://common-lisp.net> >> > change in the last week? I don't see any relevant news on >> > common-lisp.net <http://common-lisp.net>. >> > >> Commit messages seem to be working again. Thanks! >> >> Comments on issues and merges aren't getting sent still >> though. >> >> >> Bizarre. I have no idea that anybody did anything... >> @Common-Lisp.net Administration Mailing List >> <mailto:[email protected]> did you? > I didn't send any email to that list. Should I have? > > > > -- > Bye, > > Erik. > > http://efficito.com -- Hosted accounting and ERP. > Robust and Flexible. No vendor lock-in. >