public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Romash, Cliff" <romash@rbbn.com>
To: Mark Wielaard <mark@klomp.org>,
	Overseers mailing list <overseers@sourceware.org>
Subject: RE: [EXTERNAL] Re: Bugzilla account
Date: Wed, 29 Jun 2022 16:23:56 +0000	[thread overview]
Message-ID: <CO3PR03MB6742C444A0B11DC7DBDCE52AA3BB9@CO3PR03MB6742.namprd03.prod.outlook.com> (raw)
In-Reply-To: <850becc397296cf0fa9478ed1e2d3d6d3cb5fd22.camel@klomp.org>

All set, thanks

-----Original Message-----
From: Mark Wielaard <mark@klomp.org> 
Sent: Wednesday, June 29, 2022 12:09 PM
To: Overseers mailing list <overseers@sourceware.org>
Cc: Romash, Cliff <romash@rbbn.com>
Subject: [EXTERNAL] Re: Bugzilla account

Hi Cliff,

On Wed, 2022-06-29 at 15:11 +0000, Romash, Cliff via Overseers wrote:
> I have a sourceware account for libc-help, but want to file a bug for
> libc. Can I please get an account for 
> https://clicktime.symantec.com/3XrnGkJij5cGvr3bbbaLEsT6Gu?u=https%3A%2F%2Fsourceware.org%2Fbugzilla%2F

A bugzilla account has been created for you. You should have gotten an
email about it. You can activate your account through the Forgot/Reset
Password link.

Cheers,

Mark

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 16:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29 15:11 Romash, Cliff
2022-06-29 16:09 ` Mark Wielaard
2022-06-29 16:23   ` Romash, Cliff [this message]

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=CO3PR03MB6742C444A0B11DC7DBDCE52AA3BB9@CO3PR03MB6742.namprd03.prod.outlook.com \
    --to=romash@rbbn.com \
    --cc=mark@klomp.org \
    --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).