From: Joseph Myers <joseph@codesourcery.com>
To: <newlib@sourceware.org>
Cc: <cygwin@cygwin.com>, <binutils@sourceware.org>,
<gdb@sourceware.org>, <gcc@gcc.gnu.org>
Subject: Re: Newlib/Cygwin now under GIT
Date: Tue, 10 Mar 2015 17:03:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1503101658200.5129@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20150310153846.GI5732@calimero.vinschen.de>
On Tue, 10 Mar 2015, Corinna Vinschen wrote:
> Hi fellow developers,
>
>
> I'm happy to inform you that the move of Newlib/Cygwin from the src CVS
> repository to the new, combined GIT repository is now final.
I note that this repository includes the include/ directory, in its larger
binutils-gdb form rather than the smaller GCC form.
How much of this is actually relevant for newlib? Mostly it relates to
libiberty and object file formats, for use of code that's not included in
this repository (which does not include libiberty). If little or none of
this code is actually used in newlib, it might make sense to remove the
unused files so it's clear they do not need merging from the other
repositories.
(Apart from include/, various shared toplevel files and directories are
out of sync between the three repositories - GCC, binutils-gdb,
newlib-cygwin - and could do with someone identifying unmerged changes and
applying them to the repositories missing them.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2015-03-10 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150305145541.GA20560@calimero.vinschen.de>
2015-03-10 15:38 ` Corinna Vinschen
2015-03-10 16:20 ` Joel Sherrill
2015-03-10 18:25 ` Corinna Vinschen
2015-03-10 17:03 ` Joseph Myers [this message]
2015-03-10 18:19 ` Corinna Vinschen
2015-03-10 18:30 ` DJ Delorie
2015-03-10 20:16 ` 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=alpine.DEB.2.10.1503101658200.5129@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=cygwin@cygwin.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.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).