unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: help-emacs-windows@gnu.org,
	David Vanderschel <DvdS@austin.rr.com>,
	rms@gnu.org, drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Re: [h-e-w] Windows Binaries
Date: Thu, 4 Oct 2012 10:05:24 +0200	[thread overview]
Message-ID: <CAH8Pv0g7jOk205Yvc4DmDRVTc_LJ-d7xxuNzSfK_Y3b-_G+73A@mail.gmail.com> (raw)
In-Reply-To: <506D1212.1090903@cs.ucla.edu>

On Thu, Oct 4, 2012 at 6:35 AM, Paul Eggert <eggert@cs.ucla.edu> wrote:
> If Dropbox is used to distribute Windows binaries,
> I suggest that any announcement of a new distribution
> contain a URL that anybody can use, without Javascript.
> That will make it more convenient for many users.

Sure, I can provide the file-specific URL, but actually my intention
was not to send announcements to this mailing list each time I upload
a new build, but rather provide (once) that base URL (which is
constant) and let people check that repository whenever they want.

According to David Vanderschel, it is possible to access to the base
URL without using Javascript at all, so I fail to see where the
problem is.

In any case, if someone ever has a problem accessing that repository,
let me know and I'll provide the file-specific URL.

-- 
Dani Moncayo



  reply	other threads:[~2012-10-04  8:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11 17:26 Windows Binaries Drew Adams
2012-08-06 14:53 ` Drew Adams
2012-08-08 20:23   ` Dani Moncayo
2012-08-24 14:46   ` Drew Adams
2012-08-26 17:02     ` Dani Moncayo
2012-10-01 21:13     ` [h-e-w] " Drew Adams
2012-10-02 18:04       ` Dani Moncayo
2012-10-03  1:13         ` Richard Stallman
2012-10-03  6:42           ` Dani Moncayo
2012-10-04  1:34           ` David Vanderschel
2012-10-04  4:35             ` Paul Eggert
2012-10-04  8:05               ` Dani Moncayo [this message]
2012-10-04 15:59                 ` Paul Eggert
2012-10-04  8:09             ` Richard Stallman
2012-10-09 20:37         ` Dani Moncayo
  -- strict thread matches above, loose matches on Subject: below --
2011-12-07  3:27 emacs-20111206-r106632 " Christoph Scholtes
2011-12-31 22:38 ` Drew Adams
2012-02-13 15:43   ` Drew Adams
2012-02-15  1:32     ` Christoph Scholtes
2012-02-15  1:34       ` [h-e-w] " Drew Adams
2012-03-13 18:01       ` Drew Adams
2012-03-18 21:26         ` Dani Moncayo
2012-03-19  0:22           ` [h-e-w] " Drew Adams
2012-04-01 17:28         ` Drew Adams
2012-06-29 14:45           ` [h-e-w] " Drew Adams
2012-06-29 14:55             ` Christoph Scholtes
2012-06-29 15:02               ` [h-e-w] " 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=CAH8Pv0g7jOk205Yvc4DmDRVTc_LJ-d7xxuNzSfK_Y3b-_G+73A@mail.gmail.com \
    --to=dmoncayo@gmail.com \
    --cc=DvdS@austin.rr.com \
    --cc=drew.adams@oracle.com \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=help-emacs-windows@gnu.org \
    --cc=rms@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).