From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Jeff Law <law@redhat.com>
Cc: John Marino <gnugcc@marino.st>,
"Joseph S. Myers" <joseph@codesourcery.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Gerald Pfeifer <gerald@pfeifer.com>,
"manu at gcc dot gnu.org" <manu@gcc.gnu.org>,
"Eric Botcazou (gnu.org)" <ebotcazou@gcc.gnu.org>
Subject: Re: Contributing new gcc targets: i386-*-dragonfly and x86-64-*-dragonfly
Date: Tue, 13 May 2014 14:10:00 -0000 [thread overview]
Message-ID: <CAH6eHdSWr8MyhEbPe24ZAxLH8hUDzwtKT0M7uwF_CDgL0j=C3g@mail.gmail.com> (raw)
In-Reply-To: <53710158.10305@redhat.com>
On 12 May 2014 18:14, Jeff Law wrote:
> On 05/12/14 11:10, John Marino wrote:
>>
>> On 5/12/2014 18:59, Jeff Law wrote:
>>>
>>> On 05/09/14 01:14, John Marino wrote:
>>>>
>>>>
>>>> 1) Patch updated online as requested
>>>> 2) At this exact point in time, we probably can share the files
>>>> 3) I might debate that we should share the files - that would imply
>>>> reviewing the existing counterpart files for NetBSD and OpenBSD and
>>>> combining when equivalent.
>>>
>>> Let's go ahead and keep the files separate. We can always go back and
>>> combine them at a later date if we see the need.
>>>
>>> So with that in mind, the patch is good to go with the gnat thread stuff
>>> removed.
>>>
>>> Do you have write access, or do you you need someone to commit the
>>> change for you?
>>
>>
>> Thanks, Jeff!
>> I do not have write access, but jwakely has graciously offered to commit
>> this patchset when it achieves approval, so I guess he's on deck!
>
> OK. It's Jon's :-)
Great, I'll coordinate with John and aim to get it committed before Friday.
next prev parent reply other threads:[~2014-05-13 14:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-19 19:41 John Marino
2014-04-20 19:05 ` Jonathan Wakely
2014-04-21 4:41 ` John Marino
2014-04-29 15:39 ` [PING] " John Marino
2014-04-29 17:25 ` Ian Lance Taylor
2014-04-29 18:50 ` John Marino
2014-04-30 0:07 ` Ian Lance Taylor
2014-05-01 23:03 ` Joseph S. Myers
2014-05-01 23:46 ` John Marino
2014-05-02 17:49 ` Joseph S. Myers
2014-05-02 18:17 ` John Marino
2014-05-02 20:15 ` Joseph S. Myers
2014-05-02 20:20 ` John Marino
2014-05-03 7:12 ` John Marino
2014-05-08 13:15 ` Jonathan Wakely
2014-05-08 13:32 ` Jeff Law
2014-05-08 13:36 ` John Marino
2014-05-09 5:27 ` Jeff Law
2014-05-09 7:15 ` John Marino
2014-05-12 16:59 ` Jeff Law
2014-05-12 17:10 ` John Marino
2014-05-12 17:14 ` Jeff Law
2014-05-13 14:10 ` Jonathan Wakely [this message]
2014-05-21 11:43 ` Jonathan Wakely
2015-04-09 20:12 ` [doc] Add John Marino to doc/contrib.texi (was: Contributing new gcc targets: i386-*-dragonfly and x86-64-*-dragonfly) Gerald Pfeifer
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='CAH6eHdSWr8MyhEbPe24ZAxLH8hUDzwtKT0M7uwF_CDgL0j=C3g@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=ebotcazou@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=gnugcc@marino.st \
--cc=joseph@codesourcery.com \
--cc=law@redhat.com \
--cc=manu@gcc.gnu.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).