From: Jesse Davidson <jdavidson@madberry.com>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: Broken link on ecos.sourceware.org
Date: Sat, 13 Feb 2021 14:56:07 +0000 [thread overview]
Message-ID: <CAFWRzo3uthQfy7_d3ENd77nDn9TjpYW9nsAbE8bKbPUAS4O9aw@mail.gmail.com> (raw)
In-Reply-To: <CAFWRzo1oe9Jy8NZA_hpkFZKCy3aassxm_2hoL0cTL6gH6FBmUg@mail.gmail.com>
I wanted to check in and see if you got my note about the broken link on
your site?
Thanks,
Jesse
On Tuesday, February 9, 2021 at 10:28 AM, Jesse Davidson <
jdavidson@madberry.com> wrote:
> I noticed that you have a broken link to a website called DalSemi.com.
> That site was first published way back in 1996 but unfortunately, it is no
> longer a working website.
>
> You link to DalSemi on this page: http://ecos.sourceware.org/hardware.html
>
> We recently published an article that explains what happened to the site
> and how Maxim Integrated grew its way onto the NASDAQ 100 through
> acquisitions. I think it's an interesting story, and it could be useful to
> your readers.
>
> Here's the article if you want to take a look:
> https://www.wellpcb.com/Appetite-for-Acquisition-How-Maxim-Integrated-Bought-Its-Way-Into-the-NASDAQ-Top-100.html
>
> Would you consider swapping out the broken link for our article?
>
> Cheers,
> Jesse
>
> --
> Jesse Davidson, Editor
> 5 Ross Rd
> Durham, NH 03824
>
> PS: if you didn't like getting this email, please just shoot me a note and
> ask me not to email you anymore. I'll make sure I don't.
>
next prev parent reply other threads:[~2021-02-13 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 18:28 Jesse Davidson
2021-02-13 14:56 ` Jesse Davidson [this message]
2021-02-16 20:23 ` Jesse Davidson
2021-02-20 15:32 ` Jesse Davidson
-- strict thread matches above, loose matches on Subject: below --
2020-11-18 21:34 Rachel Cook
2020-11-22 21:59 ` Rachel Cook
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=CAFWRzo3uthQfy7_d3ENd77nDn9TjpYW9nsAbE8bKbPUAS4O9aw@mail.gmail.com \
--to=jdavidson@madberry.com \
--cc=ecos-discuss@ecos.sourceware.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).