public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Romash, Cliff" <romash@rbbn.com>
To: "overseers@sourceware.org" <overseers@sourceware.org>
Subject: Bugzilla account
Date: Wed, 29 Jun 2022 15:11:10 +0000	[thread overview]
Message-ID: <CO3PR03MB674206DED99202891E6D7D41A3BB9@CO3PR03MB6742.namprd03.prod.outlook.com> (raw)

I have a sourceware account for libc-help, but want to file a bug for libc. Can I please get an account for https://sourceware.org/bugzilla/

Thanks.

Cliff Romash
Ribbon Communications

Notice: This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments.

             reply	other threads:[~2022-06-29 15:11 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29 15:11 Romash, Cliff [this message]
2022-06-29 16:09 ` Mark Wielaard
2022-06-29 16:23   ` [EXTERNAL] " Romash, Cliff
  -- strict thread matches above, loose matches on Subject: below --
2022-08-16 14:11 Marcin Copik
2022-08-16 14:40 ` Frank Ch. Eigler
2022-08-06 16:41 John Brooks
2022-08-06 23:49 ` Mark Wielaard
2022-05-31  4:08 Robin Gareus
2022-05-31  6:44 ` Mark Wielaard
     [not found] <1998972755.111970.1652937238331.ref@mail.yahoo.com>
2022-05-19  5:13 ` BogDan
2022-05-19  9:24   ` Mark Wielaard
2022-05-19 10:00     ` BogDan
2022-03-17 23:56 Luca Boccassi
2022-03-18 11:17 ` Mark Wielaard
2022-03-18 11:38   ` Luca Boccassi
2022-03-10 21:02 Brendan Shanks
2022-03-10 21:41 ` Mark Wielaard
2022-03-08  9:32 Anna “CyberTailor”
2022-03-08 12:21 ` Mark Wielaard
2022-02-23 23:21 bugzilla account dann frazier
2022-02-23 23:28 ` Mark Wielaard
2022-02-23 23:59   ` Frank Ch. Eigler
2022-02-24  4:11     ` dann frazier
2022-02-15  8:31 Jan Palus
2022-02-15 10:40 ` Mark Wielaard
2022-02-15 11:03   ` Jan Palus
2022-02-03  6:43 Bugzilla Account Andreas Schneider
2022-02-03 11:54 ` Mark Wielaard
2022-01-27 14:36 Bugzilla account Martin Mareš
2022-01-27 14:48 ` Mark Wielaard
2017-06-26 13:52 Marcin M.
2014-12-26 14:51 bugzilla account Andrew Senkevich
2014-12-09 16:08 Bugzilla account Grósz Dániel
2011-02-23 10:02 Bugzilla Account isahib
2011-02-23 12:55 ` Ian Lance Taylor
     [not found] <OFD58FD8D5.C092494D-ONC22573C4.00542C5F-C22573C4.00550A87@il.ibm.com>
2008-01-02 17:05 ` Bugzilla account Daniel Berlin
2008-01-02 19:12   ` Olga Golovanevsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CO3PR03MB674206DED99202891E6D7D41A3BB9@CO3PR03MB6742.namprd03.prod.outlook.com \
    --to=romash@rbbn.com \
    --cc=overseers@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).