The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: ACM opens up much of its archives
Date: Thu, 26 May 2022 16:43:05 -0400	[thread overview]
Message-ID: <CAEoi9W7wNBY4cJnWduMhgj=+JE_AGRYH5eih8nBQfw+qaFssfA@mail.gmail.com> (raw)
In-Reply-To: <CAKH6PiWcDMdbr6Zg6Oy7nfVarAyB1gwpBhb9Ef=ZkRwTfKL0GA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 624 bytes --]

On Thu, May 26, 2022 at 4:40 PM Douglas McIlroy <
douglas.mcilroy@dartmouth.edu> wrote:

> >> If you’re a *current* member of these societies then you should have
> good access to journal content.
>
> >I believe this is true for ACM, but for IEEE not so much. You have to pay
> for a digital library membership _in addition to_ your standard membership
>
> ACM is the same.  At $99/year membership is a bargain by ordinary
> professional society standards. But they charge an additional $99 for
> access to 21st-century Digital Library.content.
>

Sigh. I stand corrected. Thanks, Doug.

        - Dan C.

[-- Attachment #2: Type: text/html, Size: 966 bytes --]

  reply	other threads:[~2022-05-26 20:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26 20:39 [TUHS] " Douglas McIlroy
2022-05-26 20:43 ` Dan Cross [this message]
2022-05-26 20:53 ` [TUHS] " Clem Cole
2022-05-26 21:13   ` Charles H Sauer (he/him)
  -- strict thread matches above, loose matches on Subject: below --
2022-05-24 23:29 [TUHS] " arnold
2022-05-25 15:53 ` [TUHS] " Clem Cole
2022-05-25 16:00   ` Richard Salz
2022-05-25 16:01     ` Clem Cole
2022-05-26  1:54   ` Larry McVoy
2022-05-26 17:09   ` Henry Mensch
2022-05-26 17:13     ` Dan Cross
2022-05-26 19:49       ` Stephen Kitt

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='CAEoi9W7wNBY4cJnWduMhgj=+JE_AGRYH5eih8nBQfw+qaFssfA@mail.gmail.com' \
    --to=crossd@gmail.com \
    --cc=douglas.mcilroy@dartmouth.edu \
    --cc=tuhs@tuhs.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 NNTP newsgroup(s).