From: Iain Buclaw <ibuclaw@gdcproject.org>
To: Jeff Law <law@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 3/13] D: The front-end (GDC) changelogs.
Date: Mon, 11 Sep 2017 17:39:00 -0000 [thread overview]
Message-ID: <CABOHX+dVFdH6YbQRqXtAJnzY-vY7dZo1K8Q6HWGA=hy+O0NR=A@mail.gmail.com> (raw)
In-Reply-To: <40b7d841-9272-1f8a-4563-b1b7c41c09a7@redhat.com>
On 11 September 2017 at 17:43, Jeff Law <law@redhat.com> wrote:
> On 05/28/2017 03:11 PM, Iain Buclaw wrote:
>> This patch just includes all changelogs for the D front-end (GDC),
>> going back to the dawn of time itself.
>>
>> Change logs for the DMD front-end and libraries are kept on the dlang site.
> Your call on how much of the historical record you want to keep.
>
> jeff
I'll paraphrase the words of Alan at the Cauldron last weekend: Would
you want your name removed from the Changelog without you knowing?
This front-end has been going for over a decade now, and I wouldn't
feel comfortable removing the original authors from that history.
Iain.
next prev parent reply other threads:[~2017-09-11 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-28 21:12 Iain Buclaw
2017-09-11 15:43 ` Jeff Law
2017-09-11 17:39 ` Iain Buclaw [this message]
2017-09-12 17:10 ` Jeff Law
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+dVFdH6YbQRqXtAJnzY-vY7dZo1K8Q6HWGA=hy+O0NR=A@mail.gmail.com' \
--to=ibuclaw@gdcproject.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@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).