From: Andrew Haley <aph@redhat.com>
To: tromey@redhat.com
Cc: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
NightStrike <nightstrike@gmail.com>,
Andreas Tobler <andreast-list@fgznet.ch>,
Dave Korn <dave.korn.cygwin@googlemail.com>,
Anthony Green <green@moxielogic.com>,
Anthony Green <green@redhat.com>,
libffi-discuss@sourceware.org,
gcc-patches <gcc-patches@gcc.gnu.org>,
Java Patch List <java-patches@gcc.gnu.org>
Subject: Re: libffi merge
Date: Mon, 08 Jun 2009 16:35:00 -0000 [thread overview]
Message-ID: <4A2D3DAA.503@redhat.com> (raw)
In-Reply-To: <m31vpur90n.fsf@fleche.redhat.com>
Tom Tromey wrote:
>>>>>> "Ralf" == Ralf Wildenhues <Ralf.Wildenhues@gmx.de> writes:
>
> Ralf> Would standalone libffi be willing to accept into its tree
> Ralf> configury parts that are only active in the GCC tree?
>
> If this is possible, why have a separate libffi repository at all?
> You could just tell developers to:
>
> svn co svn://gcc.gnu.org/svn/gcc/trunk/libffi
And we'd have to check into gcc bits of configury that are no longer
relevant to gcc. But I'm looking at all possibilities.
Anyway, if the repos are not massively different then merging is trivial.
Andrew.
next prev parent reply other threads:[~2009-06-08 16:35 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 17:10 Andrew Haley
2009-06-03 11:03 ` Andrew Haley
2009-06-03 11:54 ` Anthony Green
2009-06-03 19:53 ` Andrew Haley
2009-06-03 20:26 ` Anthony Green
2009-06-04 10:35 ` Andrew Haley
2009-06-04 10:42 ` Andrew Haley
2009-06-04 10:57 ` Andrew Haley
2009-06-04 12:39 ` Anthony Green
2009-06-04 12:49 ` Andrew Haley
2009-06-04 14:09 ` Dave Korn
2009-06-04 14:43 ` Andrew Haley
2009-06-04 15:07 ` Andrew Haley
2009-06-04 15:41 ` Andrew Haley
2009-06-04 16:04 ` Andrew Haley
2009-06-04 16:11 ` Dave Korn
2009-06-04 16:27 ` Andrew Haley
2009-06-04 16:36 ` Andrew Haley
2009-06-04 17:04 ` Andrew Haley
2009-06-04 17:46 ` Timothy Wall
2009-06-04 17:26 ` Andrew Haley
2009-06-05 12:12 ` Dave Korn
2009-06-05 12:53 ` Andrew Haley
2009-06-05 13:03 ` Andrew Haley
2009-06-05 13:40 ` Andrew Haley
2009-06-05 17:24 ` Andreas Tobler
2009-06-05 17:37 ` Andrew Haley
2009-06-06 2:58 ` NightStrike
2009-06-06 8:22 ` Andrew Haley
2009-06-07 6:44 ` Ralf Wildenhues
2009-06-08 16:22 ` Tom Tromey
2009-06-08 16:35 ` Andrew Haley [this message]
2009-06-08 16:54 ` NightStrike
2009-06-08 17:01 ` Andrew Haley
2009-06-08 17:58 ` NightStrike
2009-06-08 18:57 ` Timothy Wall
2009-06-08 22:21 ` Timothy Wall
2009-06-09 15:32 ` Andrew Haley
2009-06-09 16:36 ` Timothy Wall
2009-06-09 16:44 ` Andrew Haley
2009-06-09 18:08 ` PATCH libffi testsuite closure fixes Timothy Wall
2009-06-09 18:08 ` PATCH libffi win64 support Timothy Wall
2009-06-10 9:45 ` Andrew Haley
2009-06-10 10:54 ` Timothy Wall
2009-06-12 14:21 ` Andrew Haley
2009-06-12 15:02 ` Timothy Wall
2009-06-12 15:08 ` Kai Tietz
2009-06-12 15:17 ` Andrew Haley
2009-06-12 15:23 ` Timothy Wall
2009-06-12 15:44 ` Andrew Haley
2009-06-12 15:46 ` NightStrike
2009-06-12 15:53 ` Andrew Haley
2009-06-12 19:17 ` Timothy Wall
2009-06-12 20:03 ` Andrew Haley
2009-06-12 20:31 ` Timothy Wall
2009-06-16 15:57 ` NightStrike
2009-06-16 16:03 ` NightStrike
2009-06-16 16:26 ` Andrew Haley
2009-06-16 17:58 ` Ralf Wildenhues
2009-06-16 18:20 ` Andrew Haley
2009-06-16 19:11 ` Ralf Wildenhues
2009-06-17 12:36 ` Dave Korn
2009-06-17 12:53 ` Andrew Haley
2009-06-17 14:21 ` Dave Korn
2009-06-17 17:51 ` autom4te caching (was: PATCH libffi win64 support) Ralf Wildenhues
2009-06-16 16:31 ` PATCH libffi win64 support Andrew Haley
2009-06-16 17:19 ` NightStrike
2009-06-16 17:37 ` Andrew Haley
2009-06-16 17:38 ` NightStrike
2009-06-16 17:42 ` NightStrike
2009-06-16 17:57 ` Ralf Wildenhues
2009-06-17 2:24 ` NightStrike
2009-06-08 16:48 ` libffi merge NightStrike
2009-06-08 16:50 ` NightStrike
2009-06-08 18:25 ` Ralf Wildenhues
2009-06-08 18:33 ` Andrew Haley
2009-06-08 17:03 ` Andrew Haley
2009-06-09 10:34 ` H.J. Lu
2009-06-09 10:39 ` Andrew Haley
2009-06-08 17:16 ` Andrew Haley
2009-06-09 10:16 ` Andrew Haley
2009-06-09 11:45 ` Joseph S. Myers
2009-06-09 12:14 ` Andrew Haley
2009-06-09 14:58 ` Andrew Haley
2009-06-09 17:41 ` Ralf Wildenhues
2009-06-09 15:24 ` Andrew Haley
2009-06-05 13:11 ` Dave Korn
2009-06-04 16:29 ` Andrew Haley
2009-06-04 17:47 ` Timothy Wall
2009-06-04 17:53 ` Andrew Haley
2009-06-05 12:14 ` Dave Korn
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=4A2D3DAA.503@redhat.com \
--to=aph@redhat.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=andreast-list@fgznet.ch \
--cc=dave.korn.cygwin@googlemail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=green@moxielogic.com \
--cc=green@redhat.com \
--cc=java-patches@gcc.gnu.org \
--cc=libffi-discuss@sourceware.org \
--cc=nightstrike@gmail.com \
--cc=tromey@redhat.com \
/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).