public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: newlib@sourceware.org
Subject: Re: Importing inttypes methods
Date: Wed, 26 Jul 2017 12:02:00 -0000	[thread overview]
Message-ID: <0749fb78-0757-fab0-e317-54ecae295f9c@embedded-brains.de> (raw)
In-Reply-To: <20170726110849.GG14419@calimero.vinschen.de>

On 26/07/17 13:08, Corinna Vinschen wrote:

> Oh, btw., please make sure the patches have no trailing whitespace.
> That's not really a problem, but `git am' complains about them.

I think we should keep the trailing white space if it is already in the 
original file.

-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.huber@embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

  reply	other threads:[~2017-07-26 12:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25 19:51 Aditya Upadhyay
2017-07-26 11:08 ` Corinna Vinschen
2017-07-26 12:02   ` Sebastian Huber [this message]
2017-07-26 12:02   ` Aditya Upadhyay
2017-07-26 21:24     ` Aditya Upadhyay
2017-07-27 12:32       ` Corinna Vinschen
2017-07-27 14:00         ` Aditya Upadhyay
2017-07-28 10:43           ` Corinna Vinschen
2017-07-28 11:02             ` Aditya Upadhyay
2017-07-28 11:40               ` Gedare Bloom
2017-07-28 13:08                 ` Corinna Vinschen
2017-07-28 14:28                   ` Gedare Bloom
2017-07-28 18:29                     ` Corinna Vinschen
2017-07-29 12:40                       ` Gedare Bloom
2017-07-29 13:57                         ` Aditya Upadhyay
2017-07-30  8:46                           ` Aditya Upadhyay
2017-07-30 15:41                             ` Gedare Bloom
2017-07-31 10:08                               ` Corinna Vinschen
2017-08-01  8:31                                 ` Aditya Upadhyay
2017-08-01 12:10                                   ` Gedare Bloom
2017-07-28 18:24               ` Joel Sherrill

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=0749fb78-0757-fab0-e317-54ecae295f9c@embedded-brains.de \
    --to=sebastian.huber@embedded-brains.de \
    --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).