public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Erik Soderquist <Erik.Soderquist@Dynatrace.com>
To: cygwin@cygwin.com
Cc: eli@barzilay.org
Subject: Re: Two web page issues
Date: Mon, 04 Jan 2016 18:34:00 -0000	[thread overview]
Message-ID: <CACoZoo3fCFt=xH1rj2DFWdUJFvTKE9mPXRQHpEMSc64bCv5FPw@mail.gmail.com> (raw)
In-Reply-To: <CALO-guto40G+TJ5a+=mcAeyFcN0pj1JRniUK_gjGBmy76w6Pzw@mail.gmail.com>

On Mon, Jan 4, 2016 at 1:18 PM, Eli Barzilay <eli@barzilay.org> wrote:
> (I'm not subscribed to this list, so hopefully this will work.)

I'm mildly surprised it did (see below).

> One thing that bugged me in the past is the use of "BLODA" in the FAQ
> text ("all software on the BLODA") -- since it's part of the text, an
> obvious question is what it means, and, confusingly enough, that's not
> explained in the text that BLODA links to.

https://cygwin.com/acronyms/

I don't know how this is linked to; I have it bookmarked.

> I eventually googled my way to the explanation that time -- and since
> fork issues are rare enough, it's been enough time to forget the
> meaning of that thing, so I just went down the same path.  Again.
> I'm guessing that someone thought that it'll catch on as a term,
> but it still looks like a cygwin-ism.
>
> (For extra credit, google now helpfully suggests images -- look for it
> now, then imagine that someone else looked at your screen as you're
> trying to stutter something that sounds technical.)

This extra credit assignment was ... interesting...  ;)

> It would be nice if the above text says just "all software on <this
> list>", or otherwise explains the meaning in the #faq.using.bloda entry.
>
>
>
> A second thing that could use some friendly improvement is to list the
> email address of this list in the page that describes it.  AFAICT, this
> should be https://cygwin.com/ml/cygwin/ -- but there is nowhere that I
> see there where the actual email is found...  In theory, I guess that I
> could read through https://cygwin.com/lists.html and reach the point
> where it says "Mail sent to themailinglistname@cygwin.com will go to the
> list" and guess that the "cygwin:" entry means that that's the email.
> But in practice this is as good as not being there...

I've found it before, but I'm subscribed, so... specifically not
listing the address is a common spam prevention method, and many lists
will reject (silently or otherwise) email from non-subscribed
addresses as a spam prevention method as well.

-- Erik

>
> --
>                     ((x=>x(x))(x=>x(x)))                   Eli Barzilay:
>                     http://barzilay.org/                   Maze is Life!
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2016-01-04 18:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04 18:19 Eli Barzilay
2016-01-04 18:34 ` Erik Soderquist [this message]
2016-01-04 18:45   ` Eli Barzilay
2016-01-04 19:20   ` Andrey Repin
2016-01-04 19:51     ` Erik Soderquist
2016-01-04 19:59       ` cyg Simple

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='CACoZoo3fCFt=xH1rj2DFWdUJFvTKE9mPXRQHpEMSc64bCv5FPw@mail.gmail.com' \
    --to=erik.soderquist@dynatrace.com \
    --cc=cygwin@cygwin.com \
    --cc=eli@barzilay.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).