| 1 |
On Fri, Jan 8, 2021 at 11:29 AM Thomas Deutschmann <whissi@g.o> wrote: |
| 2 |
> |
| 3 |
> On 2021-01-08 17:03, Mike Gilbert wrote: |
| 4 |
> > I strongly object to you pushing this patch as-is. There have been |
| 5 |
> > plenty of non-technical objections, including from the eclass |
| 6 |
> > maintainer. |
| 7 |
> |
| 8 |
> The eclass maintainer has disqualified himself going into a technical |
| 9 |
> debate with saying |
| 10 |
> |
| 11 |
> > So, over my dead commit access. |
| 12 |
> |
| 13 |
> in his first posting. |
| 14 |
> |
| 15 |
> This is a technical mailing list. Currently, acct-* stuff is breaking |
| 16 |
> stuff. Nobody has challenged this yet. |
| 17 |
> |
| 18 |
> Now I proposed a way how to unbreak stuff. |
| 19 |
> |
| 20 |
> Please tell me why we should keep broken stuff for non-technical reason |
| 21 |
> and cause harm for those who are affected? |
| 22 |
> |
| 23 |
> It's not like we cannot address the other stuff later. It's about |
| 24 |
> getting the fix down to users who are currently affected by this. So why |
| 25 |
> take hostage when some user(s) ignore the problem for more than a year |
| 26 |
> and show that they are not interested in collaboration to find a |
| 27 |
> solution for a technical problem they created despite warnings before |
| 28 |
> this went live? |
| 29 |
> |
| 30 |
> Of course, if you are not affected by this problem it is very easy to |
| 31 |
> relax and sit back. You have all the time in the world... but when you |
| 32 |
> are affected by this at large scale it is not that funny anymore. |
| 33 |
|
| 34 |
Let me put it this way: if you push this without agreement from the |
| 35 |
maintainer, QA, or council, you can probably expect a swift revert. |
Archives