public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Gedare Bloom <gedare@rtems.org>
To: "newlib@sourceware.org" <newlib@sourceware.org>
Subject: Re: [PATCH 1/4] Importing strtoimax inttypes method from FreeBSD.
Date: Wed, 02 Aug 2017 13:56:00 -0000	[thread overview]
Message-ID: <CAC82fA3-QA6xy4UqEDKruPD_yq4SRrwi3iwWy6_M7X=Zj0GwXA@mail.gmail.com> (raw)
In-Reply-To: <20170802110435.GH25551@calimero.vinschen.de>

On Wed, Aug 2, 2017 at 7:04 AM, Corinna Vinschen <vinschen@redhat.com> wrote:
> On Aug  2 08:49, Aditya Upadhyay wrote:
>> ---
>>  newlib/libc/include/inttypes.h |  12 +++
>>  newlib/libc/stdlib/Makefile.am |   1 +
>>  newlib/libc/stdlib/strtoimax.c | 167 +++++++++++++++++++++++++++++++++++++++++
>
> All 4 patches applied.
>
> I made a few minor formatting changes in terms of whitespaces and
> missing empty lines between functions.  Please compare what I commited
> with your local patch to see the differences.
>
Thanks. There were no empty lines between functions in the original
BSD source. However, since the original source was not submitted
separately from the modification to make it useful, this is hard to
see. Best to leave it as you have pushed it I suppose.

Aditya, if there are more patches in the future please first provide a
commit with the unmodified BSD file, and then a second commit to
modify the file and to add it to the build system. I neglected to
follow-up on this procedure with you, but it is a good way to ensure
tight synchronization with upstream sources.

-Gedare

>
> Thanks,
> Corinna
>
> --
> Corinna Vinschen
> Cygwin Maintainer
> Red Hat

  reply	other threads:[~2017-08-02 13:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02  3:20 Aditya Upadhyay
2017-08-02 11:04 ` Corinna Vinschen
2017-08-02 13:56   ` Gedare Bloom [this message]
2017-08-02 14:06     ` Aditya Upadhyay
2017-08-11  6:32   ` Sebastian Huber
2017-08-11  7:11     ` Aditya Upadhyay
2017-08-11  8:24     ` Corinna Vinschen

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='CAC82fA3-QA6xy4UqEDKruPD_yq4SRrwi3iwWy6_M7X=Zj0GwXA@mail.gmail.com' \
    --to=gedare@rtems.org \
    --cc=newlib@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).