From: Florian Weimer <fweimer@redhat.com>
To: PRASANTH R via Libc-help <libc-help@sourceware.org>
Cc: PRASANTH R <ragaprasanth@gmail.com>
Subject: Re: Bug 26517 - timezone: Fix zdump duplicate binary
Date: Mon, 23 Nov 2020 12:00:11 +0100 [thread overview]
Message-ID: <87d004bao4.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <CAG7eodHm9EJ6NHNoRpBMNp+7thzu=JX46ZiD6bp3yR3+E3TMTQ@mail.gmail.com> (PRASANTH R. via Libc-help's message of "Mon, 16 Nov 2020 09:14:10 +0530")
* PRASANTH R. via Libc-help:
> This was my first patch, just curious to see the review on this. kindly
> find the attachment
Thank you for your patch. Please re-post it to the libc-alpha list,
and add a NEWS entry in the “Deprecated and removed features, and other
changes affecting compatibility” section. Thanks.
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
prev parent reply other threads:[~2020-11-23 11:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 3:44 PRASANTH R
2020-11-23 11:00 ` Florian Weimer [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=87d004bao4.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-help@sourceware.org \
--cc=ragaprasanth@gmail.com \
/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).