public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH][Newlib][libgloss] - Semihosting v2 general build changes (1 / 5)
Date: Wed, 05 Jul 2017 08:36:00 -0000	[thread overview]
Message-ID: <20170705083621.GB30902@calimero.vinschen.de> (raw)
In-Reply-To: <VI1PR0801MB20317561107C26F7B366DFFAFFD60@VI1PR0801MB2031.eurprd08.prod.outlook.com>

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

Hi Tamar,

On Jul  3 16:53, Tamar Christina wrote:
> Hi All, 
> 
> 
> This patch adds the general build system changes needed 
> in order to compile and create the new libraries for Semihosting v2.
> 
> This works by creating a similar recursive make target that is modeled
> after the existing multilib makefile config-ml.in.
> 
> OK for master?
> 
> PS. I do not have commit rights so if OK can someone apply for me?
> 
> Thanks,
> Tamar
> 
> 
> libgloss/
> 2017-07-03  Tamar Christina  <tamar.christina@arm.com>
> 
> 	* multi-build.in (multi-do): New.

We don't use ChangeLog format anymore.  Rather we would prefer
informative git commit messages and patches in `git format-patch'
format.

These 5 patches qualify as patch series, so it would be nice if
you could resend them that way.


Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer
Red Hat

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

  reply	other threads:[~2017-07-05  8:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03 16:53 Tamar Christina
2017-07-05  8:36 ` Corinna Vinschen [this message]
2017-07-05  8:44   ` Tamar Christina
2017-07-05 12:13     ` Tamar Christina
2017-07-05 12:42       ` Corinna Vinschen
2017-07-05 13:32     ` [Newlib][libgloss]ARM - semihosting use of __end__symbol in crt0.S Dave Nadler
2017-07-05 15:16       ` Tamar Christina
2017-07-05 18:19         ` Dave Nadler
2017-07-06  4:42           ` Senthil Kumar Selvaraj
2017-07-06 14:22             ` Tamar Christina

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=20170705083621.GB30902@calimero.vinschen.de \
    --to=vinschen@redhat.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).