public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Cc: Andrew Jenner <andrew@codesourcery.com>
Subject: Re: [PATCH] ia16 target
Date: Mon, 03 Apr 2017 08:38:00 -0000	[thread overview]
Message-ID: <20170403083808.GB20833@calimero.vinschen.de> (raw)
In-Reply-To: <29c1de0e-2ec6-229b-602e-63943f8a4521@codesourcery.com>

[-- Attachment #1: Type: text/plain, Size: 972 bytes --]

On Apr  1 20:26, Andrew Jenner wrote:
> I've posted patches to gcc-patches for adding an ia16 (16-bit x86) port to
> GCC (see https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00009.html). Here are
> the corresponding newlib changes, based on those contributed (but not
> committed) by Rask Ingemann Lambertsen 10 years ago.
> 
> These changes add a BSP (for DOS), startup code and linker script (for .com
> files) to libgloss, and optimized string functions.
> 
> Okay to commit?
> 
> The patch was too large to send by email, but I've uploaded it to:
> 
> https://sourcery.mentor.com/GNUToolchain/package14963/public/ia16-elf/newlib_ia16.patch

Not in this form, no.  Please create smaller, logical  patch units.
Create the patches as a git patch series with meaningful log messages
for each patch in the series.  Then send the series (which will then
easily fit into mails) to this list.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2017-04-03  8:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-01 19:26 Andrew Jenner
2017-04-03  8:38 ` Corinna Vinschen [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=20170403083808.GB20833@calimero.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=andrew@codesourcery.com \
    --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).