From: Mathias Dahl <mathias.dahl@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Christoph Scholtes <cschol2112@googlemail.com>, emacs-devel@gnu.org
Subject: Re: Emacs Windows barebin distribution
Date: Sun, 18 Nov 2012 20:56:54 +0100 [thread overview]
Message-ID: <CABrcCQ5Uk0tSJ2-MmkLBADV0sKa1c+Qd3diiGZmvOgKFUZB3wQ@mail.gmail.com> (raw)
In-Reply-To: <837gpj0vyo.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]
>
> > Would it be possible to check the access logs to see how many people
> > actually download the barebin files?
>
> Since I wrote the mail to which you responded, 7 months have passed
> and no one complained. I think by now it should be clear that no one
> needs this.
>
I'm sorry for not noticing that. I don't know why Gmail decided to show me
that old e-mail all of a
sudden, I normally delete old e-mails from this list, not archive them, but
maybe "something"
happened.
I see there have been some arguing about your reply to my reply above,
and I'm not sure what to
say, so I'll try not to say too much about it ;) I just happened to see
your proposal of "testing" the
users and thought it would be much more natural to check the download logs,
which I assumed was
under control of whoever runs that server. A few "greps" (or whatever) and
some counts on those
logs and you would know, not for sure, but it would seem like a better
measurement than the planned
"test".
However, if the concept of the barebins were broken in some sense (that's
how I interpret your and
others' replies here), it's not anything worth arguing over.
[-- Attachment #2: Type: text/html, Size: 1624 bytes --]
next prev parent reply other threads:[~2012-11-18 19:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 14:28 Emacs Windows barebin distribution Christoph Scholtes
2012-04-15 16:18 ` Eli Zaretskii
2012-11-16 22:48 ` Dani Moncayo
2012-11-16 22:54 ` Dani Moncayo
2012-11-17 7:50 ` Eli Zaretskii
2012-11-17 8:27 ` Dani Moncayo
2012-11-17 8:56 ` Eli Zaretskii
2012-11-18 12:52 ` Mathias Dahl
2012-11-18 15:30 ` Eli Zaretskii
2012-11-18 15:50 ` Drew Adams
2012-11-18 16:20 ` Juanma Barranquero
2012-11-18 17:12 ` Eli Zaretskii
2012-11-18 17:37 ` Drew Adams
2012-11-18 17:55 ` Eli Zaretskii
2012-11-18 18:22 ` Drew Adams
2012-11-18 19:00 ` Eli Zaretskii
2012-11-18 17:22 ` Drew Adams
2012-11-18 17:29 ` Juanma Barranquero
2012-11-18 17:39 ` Drew Adams
2012-11-18 17:45 ` Juanma Barranquero
2012-11-18 18:22 ` Drew Adams
2012-11-19 4:02 ` Stephen J. Turnbull
2012-11-18 17:36 ` Eli Zaretskii
2012-11-20 13:58 ` Jason Rumney
2012-11-21 4:23 ` Stephen J. Turnbull
2012-11-18 19:56 ` Mathias Dahl [this message]
2012-11-18 20:22 ` Dani Moncayo
2012-11-18 20:45 ` Dani Moncayo
2012-11-18 21:28 ` Eli Zaretskii
2012-11-18 21:14 ` Eli Zaretskii
2012-04-15 16:43 ` Jambunathan K
2012-04-16 0:02 ` Drew Adams
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABrcCQ5Uk0tSJ2-MmkLBADV0sKa1c+Qd3diiGZmvOgKFUZB3wQ@mail.gmail.com \
--to=mathias.dahl@gmail.com \
--cc=cschol2112@googlemail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).