* Re: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master) [not found] ` <Y9djb4iMA8kySL0F@troutmask.apl.washington.edu> @ 2023-01-30 13:46 ` Sam James 2023-01-31 2:31 ` Jerry D [not found] ` <e5e8e6d1dbde5e24246eba9b964b3af3627a6ee3.camel@klomp.org> 1 sibling, 1 reply; 5+ messages in thread From: Sam James @ 2023-01-30 13:46 UTC (permalink / raw) To: sgk; +Cc: Jerry D, GCC Mailing List, buildbot [-- Attachment #1: Type: text/plain, Size: 530 bytes --] > On 30 Jan 2023, at 06:27, Steve Kargl via Gcc <gcc@gcc.gnu.org> wrote: Hi Steve, > Please remove the skull and cross bones in the subject line. This is a sourceware project so I've CC'd the buildbot mailing list where we discuss these matters. Does the emoji bother you, or is it the skull and crossbones specifically (which is a recognised symbol for a hazard)? Note that this is the default upstream from the Buildbot project (we use their software) too. We haven't chosen it ourselves. Thanks, sam [-- Attachment #2: Message signed with OpenPGP --] [-- Type: application/pgp-signature, Size: 358 bytes --] ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master) 2023-01-30 13:46 ` ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master) Sam James @ 2023-01-31 2:31 ` Jerry D 0 siblings, 0 replies; 5+ messages in thread From: Jerry D @ 2023-01-31 2:31 UTC (permalink / raw) To: Sam James, sgk; +Cc: GCC Mailing List, buildbot On 1/30/23 5:46 AM, Sam James wrote: > > >> On 30 Jan 2023, at 06:27, Steve Kargl via Gcc <gcc@gcc.gnu.org> wrote: > > Hi Steve, > >> Please remove the skull and cross bones in the subject line. > > This is a sourceware project so I've CC'd the buildbot mailing list where we discuss > these matters. > > Does the emoji bother you, or is it the skull and crossbones specifically (which is > a recognised symbol for a hazard)? > > Note that this is the default upstream from the Buildbot project (we use their > software) too. We haven't chosen it ourselves. > > Thanks, > sam As long as your asking it just looks stupid, childish to think anyone needs an emoji in what we try think is a professional product. ( Too informal? ) If that's not enough, how about corny, or something for 12 year olds. Yep, it's just stupid. I don't have an issue with bots, I just don't need emojis outside of my personal chats on my phone. If it is suppose to be a notification, how about just the word "Alert" or "Notice" Regards, Jerry Jerry ^ permalink raw reply [flat|nested] 5+ messages in thread
[parent not found: <e5e8e6d1dbde5e24246eba9b964b3af3627a6ee3.camel@klomp.org>]
[parent not found: <1cac0dec-e9c1-e721-52bd-40eb6b8676de@netcologne.de>]
[parent not found: <Y9fd2SBZuEKOc0TF@troutmask.apl.washington.edu>]
[parent not found: <976efc37-8d08-a1bd-40d4-e6d9af299697@pfeifer.com>]
[parent not found: <Y9hJoAKNPFU65saq@troutmask.apl.washington.edu>]
* Re: Buildbot (Sourceware): gcc - failed configure (failure) (master) [not found] ` <Y9hJoAKNPFU65saq@troutmask.apl.washington.edu> @ 2023-01-31 13:13 ` Thomas Schwinge 2023-01-31 14:38 ` LIU Hao 0 siblings, 1 reply; 5+ messages in thread From: Thomas Schwinge @ 2023-01-31 13:13 UTC (permalink / raw) To: sgk Cc: Gerald Pfeifer, Thomas Koenig, Mark Wielaard, Sam James, fortran, Jerry D, gcc, buildbot Hi! On 2023-01-30T14:50:08-0800, Steve Kargl via Fortran <fortran@gcc.gnu.org> wrote: > Does the skull and crossbones convey anymore info than the rest of > the subject line > > Buildbot (Sourceware): gcc - failed configure (failure) (master) They convey as much additional information as does (automated) colorful syntax highlighting, or (manual) source code line indentation: "none" to some, "a lot" to others. Grüße Thomas ----------------- Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955 ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Buildbot (Sourceware): gcc - failed configure (failure) (master) 2023-01-31 13:13 ` Thomas Schwinge @ 2023-01-31 14:38 ` LIU Hao 2023-01-31 20:18 ` Steve Kargl 0 siblings, 1 reply; 5+ messages in thread From: LIU Hao @ 2023-01-31 14:38 UTC (permalink / raw) To: Thomas Schwinge, sgk Cc: Gerald Pfeifer, Thomas Koenig, Mark Wielaard, Sam James, fortran, Jerry D, gcc, buildbot [-- Attachment #1.1: Type: text/plain, Size: 1166 bytes --] 在 2023-01-31 21:13, Thomas Schwinge 写道: > Hi! > > On 2023-01-30T14:50:08-0800, Steve Kargl via Fortran <fortran@gcc.gnu.org> wrote: >> Does the skull and crossbones convey anymore info than the rest of >> the subject line >> >> Buildbot (Sourceware): gcc - failed configure (failure) (master) > > They convey as much additional information as does (automated) colorful > syntax highlighting, or (manual) source code line indentation: "none" to > some, "a lot" to others. > > First, I'd argue that 'emoji characters imply spammer' makes little sense. Everyone can examine the source of all messages in this thread and their `X-Spam-Status` headers. The fact is that, so far no message had been given a tag for having emoji/bad/obfuscated characters in its subject. Second, I also agree that the skull carries NO additional information. What happened? Where did it happen? How severe was it? What should we do about it? A skull is neither descriptive nor informative, and is very unfriendly for message filters. A tag there might look much more helpful, such as [BUILDBOT] or [FAIL]. -- Best regards, LIU Hao [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 840 bytes --] ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Buildbot (Sourceware): gcc - failed configure (failure) (master) 2023-01-31 14:38 ` LIU Hao @ 2023-01-31 20:18 ` Steve Kargl 0 siblings, 0 replies; 5+ messages in thread From: Steve Kargl @ 2023-01-31 20:18 UTC (permalink / raw) To: LIU Hao Cc: Thomas Schwinge, Gerald Pfeifer, Thomas Koenig, Mark Wielaard, Sam James, fortran, Jerry D, gcc, buildbot On Tue, Jan 31, 2023 at 10:38:02PM +0800, LIU Hao wrote: > 在 2023-01-31 21:13, Thomas Schwinge 写道: > > Hi! > > > > On 2023-01-30T14:50:08-0800, Steve Kargl via Fortran <fortran@gcc.gnu.org> wrote: > > > Does the skull and crossbones convey anymore info than the rest of > > > the subject line > > > > > > Buildbot (Sourceware): gcc - failed configure (failure) (master) > > > > They convey as much additional information as does (automated) colorful > > syntax highlighting, or (manual) source code line indentation: "none" to > > some, "a lot" to others. > > > > > > First, I'd argue that 'emoji characters imply spammer' makes little sense. > Everyone can examine the source of all messages in this thread and their > `X-Spam-Status` headers. The fact is that, so far no message had been given > a tag for having emoji/bad/obfuscated characters in its subject. > The irony! Your email ended up in one of my spam folders. X-junkfilter: 20020519 X-Spammer: bodychk-domains: 126.com> domains: 126.com -- Steve ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2023-01-31 20:18 UTC | newest] Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <20230129193123.51BDE3858D35@sourceware.org> [not found] ` <1985b16e-f17d-bba6-8b57-d372f1741356@gmail.com> [not found] ` <1EC379D7-6EF4-4B27-9D8C-00CFFD115F44@gentoo.org> [not found] ` <Y9djb4iMA8kySL0F@troutmask.apl.washington.edu> 2023-01-30 13:46 ` ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master) Sam James 2023-01-31 2:31 ` Jerry D [not found] ` <e5e8e6d1dbde5e24246eba9b964b3af3627a6ee3.camel@klomp.org> [not found] ` <1cac0dec-e9c1-e721-52bd-40eb6b8676de@netcologne.de> [not found] ` <Y9fd2SBZuEKOc0TF@troutmask.apl.washington.edu> [not found] ` <976efc37-8d08-a1bd-40d4-e6d9af299697@pfeifer.com> [not found] ` <Y9hJoAKNPFU65saq@troutmask.apl.washington.edu> 2023-01-31 13:13 ` Thomas Schwinge 2023-01-31 14:38 ` LIU Hao 2023-01-31 20:18 ` Steve Kargl
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).