public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Iain Buclaw <ibuclaw@gdcproject.org>
To: Mike Stump <mikestump@comcast.net>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 08/14] Add D2 Testsuite files.
Date: Fri, 21 Sep 2018 22:22:00 -0000	[thread overview]
Message-ID: <CABOHX+fosxcH=brbvYO1pAUM7yDhdfww-JN8zxFx45zMmX3POA@mail.gmail.com> (raw)
In-Reply-To: <4D7D3635-700A-4520-8783-F185CD213B8F@comcast.net>

On 21 September 2018 at 22:54, Mike Stump <mikestump@comcast.net> wrote:
> On Sep 17, 2018, at 5:36 PM, Iain Buclaw <ibuclaw@gdcproject.org> wrote:
>>
>> This patch adds part of the D2 testsuite, which includes D source code
>> files that are considered compilable; files that are considered
>> uncompilable, but should not ICE; and files that should execute on
>> targets with crash or assertion failures.
>
> Ok.  [ not needed, you can self-review things like this no problem ]
>
> I see you are sneaking in Alice in Wonderland...
>

I had forgotten about that test.  I recall another project written in
D (Dustmite) ran into some trouble with Debian due to the Project
Gutenberg small print, which they ended up removing.

The "small print" section in the text file says:

    DISTRIBUTION UNDER "PROJECT GUTENBERG-tm"
    You may distribute copies of this etext electronically, or by
    disk, book or any other medium if you either delete this
    "Small Print!" and all other references to Project Gutenberg,
    or:
    [...]

I'll look into convincing upstream to also do the same.

Iain

  reply	other threads:[~2018-09-21 21:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-18  0:36 Iain Buclaw
2018-09-21 20:56 ` Mike Stump
2018-09-21 22:22   ` Iain Buclaw [this message]
2018-09-24 18:40     ` Mike Stump
2018-09-25  0:12       ` Iain Buclaw
2018-10-22  1:16         ` Iain Buclaw
2018-09-22 15:08 ` Florian Weimer
2018-09-22 15:49   ` Iain Buclaw

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='CABOHX+fosxcH=brbvYO1pAUM7yDhdfww-JN8zxFx45zMmX3POA@mail.gmail.com' \
    --to=ibuclaw@gdcproject.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mikestump@comcast.net \
    /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).