public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: John Marino <gnugcc@marino.st>
To: Arnaud Charlet <charlet@adacore.com>
Cc: Eric Botcazou <ebotcazou@adacore.com>,
	gcc-patches@gcc.gnu.org,  Thomas Quinot <quinot@adacore.com>
Subject: Re: [patch] Implement Ada support for DragonFly, improve it for FreeBSD
Date: Thu, 04 Jun 2015 18:24:00 -0000	[thread overview]
Message-ID: <55708F24.70704@marino.st> (raw)
In-Reply-To: <20150603090358.GB28561@adacore.com>

On 6/3/2015 11:03, Arnaud Charlet wrote:
>> Is a new submission necessary or can this be handled by committer? 
> Preferably yes. 
>> A new submission will take me a few days because I'm traveling ATM.

There was a significant amount of bitrot.  Apparently right after I
submitted the patch, many macros were adjusted by Adacore hitting the
same files and copyrights as I did.  I updated the patch set by hand and
tested it against the 31 may snapshot.  I also fixed the
TOOLS_TARGET_PAIRS issue of course.  same URL:

http://leaf.dragonflybsd.org/~marino/freebsd/gnat-dragonfly-support.diff

I also updated the suggested commit message as Eric suggested:

http://leaf.dragonflybsd.org/~marino/freebsd/gnat-dragonfly-support.msg.txt

Hopefully this patch isn't already bitrotted!

John

  reply	other threads:[~2015-06-04 17:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29 23:36 John Marino
2015-06-03  7:30 ` Eric Botcazou
2015-06-03  7:33   ` Arnaud Charlet
2015-06-03  8:25     ` John Marino
2015-06-03  9:14       ` Arnaud Charlet
2015-06-04 18:24         ` John Marino [this message]
2015-06-04 21:04           ` Arnaud Charlet
     [not found]             ` <5570AE5B.9090804@marino.st>
2015-06-08  7:31               ` Eric Botcazou
2015-06-05 13:08           ` Arnaud Charlet
2015-06-03  9:41   ` Thomas Quinot
2015-06-03 10:46     ` John Marino
2015-06-03 11:17       ` Thomas Quinot

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=55708F24.70704@marino.st \
    --to=gnugcc@marino.st \
    --cc=charlet@adacore.com \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=quinot@adacore.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).