From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "Richard @ Quality Nonsense PR Team" <pr@qualitynonsense.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Hey, spotted an out-of-date reference on gcc.gnu.org
Date: Mon, 24 Feb 2020 13:00:00 -0000 [thread overview]
Message-ID: <CAH6eHdQYX5yEx6GQ0EtJRyO9ds-0YQbHce6cX67X3vbTK4betQ@mail.gmail.com> (raw)
In-Reply-To: <44134518.or_mail@qualitynonsense.com>
You keep talking about a broken link without telling us where it is.
But I don't think we're interested anyway, that's why nobody has replied.
On Mon, 24 Feb 2020 at 12:24, Richard @ Quality Nonsense PR Team
<pr@qualitynonsense.com> wrote:
>
> Dear GCC Team,
>
> Just checking in one last time to make sure we don't get overlooked in your inbox.
>
> Is there anything stopping you from recommending our long read about Digital Equipment Corporation to your users instead of the broken DEC link, out of interest?
>
> I'm always interested in actionable feedback ;)
>
> Richard
> Digital.com
>
> On Wed, Feb 19, 2020 at 11:34 AM, Richard @ Quality Nonsense PR Team <pr@qualitynonsense.com> wrote:
>
> Dear GCC Team,
>
> I'm following up to make sure you didn't miss my email about your broken link to DEC.com. What did you think about my idea of citing our long read about Digital Equipment Corporation instead? Can I answer any questions, perhaps?
>
> Richard
> Digital.com
>
> On Thu, Feb 13, 2020 at 12:25 PM, Richard @ Quality Nonsense PR Team <pr@qualitynonsense.com> wrote:
>
> Dear GCC Team,
>
> I’m writing because you cite DEC.com in this post on GCC - but the website has been offline for 5+ years!
>
> At Digital.com, we've published a "long read" on the rise and fall of Digital Equipment Corporation, which I thought make an "easy fix" to send your readers somewhere more useful than a 404 page.
>
> It covers everything from VAX, Altavista, DEC's sale to Compaq & ultimate demise. You'll find the article here:-
>
> https://digital.com/about/dec/
>
> Would you consider citing our work to replace the broken DEC.com link, please?
>
> I think this article would keep your content current and your readers happy - love to hear what you think. Either way, thank you for your time and consideration.
>
> Best wishes,
>
> Richard
> Digital.com
> Don't want emails from us anymore? Reply to this email with the word "UNSUBSCRIBE" in the subject line.
> Digital.com, BM Box 3667 , London, Greater London, WC1N 3XX , United Kingdom
> If you don't want further emails from me, please reply with "UNSUBSCRIBE" in the subject line. Thank you.
>
> Digital.com, BM Box 3667, BM Box 3667 Greater London, WC1N 3XX , United Kingdom
> If you don't want further emails from me, please reply with "UNSUBSCRIBE" in the subject line. Thank you.
>
> Digital.com, BM Box 3667, BM Box 3667 Greater London, WC1N 3XX , United Kingdom
next prev parent reply other threads:[~2020-02-24 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 12:24 Richard @ Quality Nonsense PR Team
2020-02-24 13:00 ` Jonathan Wakely [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-19 11:34 Richard @ Quality Nonsense PR Team
2020-02-13 12:25 Richard @ Quality Nonsense PR Team
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=CAH6eHdQYX5yEx6GQ0EtJRyO9ds-0YQbHce6cX67X3vbTK4betQ@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=pr@qualitynonsense.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).