public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Shubham Jangam <shubham.jangam@druva.com>
To: overseers@sourceware.org
Subject: Sourceware Bugzilla account creation
Date: Wed, 6 Apr 2022 17:17:54 +0530	[thread overview]
Message-ID: <CADnPyvVJUjctsowdnHn3VNcA2-fZyATM+i3ZNujoDfLg75SPiw@mail.gmail.com> (raw)

Hello,

I wanted to report one issue that I am seeing with glibc's mktime function.

Could you please create my account there?


Thanks,
Shubham Jangam

-- 


This message contains confidential information and is intended only for 
the individual to whom it is addressed. If you are not the intended 
recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately by e-mail if you have received this 
e-mail by mistake and permanently delete this e-mail from your system. 
E-mail transmission cannot be guaranteed to be secure or error-free as 
information could be intercepted, corrupted, lost, destroyed, late or 
incomplete, or could contain viruses. The sender therefore does not accept 
liability for any errors or omissions in the contents of this message, 
which arise as a result of e-mail transmission. If verification is 
required, please request a hard-copy version from the sender. Druva, 
www.druva.com <http://www.druva.com/>

             reply	other threads:[~2022-04-06 11:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 11:47 Shubham Jangam [this message]
2022-04-06 12:14 ` Mark Wielaard
  -- strict thread matches above, loose matches on Subject: below --
2022-03-16 14:15 Sourceware Bugzilla Account creation Ciaran Woodward
2022-03-16 16:03 ` Mark Wielaard
2022-02-23  9:30 Sourceware Bugzilla Account Creation Tom Coldrick
2022-02-23 10:24 ` Mark Wielaard
2022-02-13  0:21 Sourceware bugzilla account creation Gabriel Ravier
2022-02-13 10:03 ` Mark Wielaard
2021-02-20 21:08 SourceWare Bugzilla " Aaron Hill

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=CADnPyvVJUjctsowdnHn3VNcA2-fZyATM+i3ZNujoDfLg75SPiw@mail.gmail.com \
    --to=shubham.jangam@druva.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).