caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Evan Martin <martine@danga.com>
To: John Goerzen <jgoerzen@complete.org>
Cc: Christophe TROESTLER <Christophe.Troestler@umh.ac.be>,
	"O'Caml Mailing List" <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml development site
Date: Fri, 7 May 2004 12:13:33 -0700	[thread overview]
Message-ID: <20040507191333.GA522@lulu> (raw)
In-Reply-To: <20040507113141.GA18068@complete.org>

On Fri, May 07, 2004 at 06:31:41AM -0500, John Goerzen wrote:
> I'd put the releases there if it was easy.  If it took lots of time,
> making me go to a website and login somewhere (I don't usually work with
> a browser open, and would prefer scriptable command-line tools), I'd
> probably not do so as often.  Here's one brainstorm:

Seconded.

> I would not store CVS there since I use Arch.  I personally wouldn't
> store Arch stuff there either; I already have my own repositories.

Thirded.  (But for those unfamiliar with it, supporting arch is no
problem; it just uses HTTP [and sftp for committing].)

> As a developer, I want something I can drive from a command line and
> automate.  I don't mind having to log in somewhere if I can do it from a
> command line.  I definately don't want to have to log in to a web site
> to post stuff, check bugs, etc.

Agreed.  Sourceforge is really painful to use because of this.  I want
to type "upload --project=myproject --package=source foo-0.1.2.tar.gz",
not click through 15 slow HTML forms.

-- 
Evan Martin
martine@danga.com
http://neugierig.org

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  parent reply	other threads:[~2004-05-07 19:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-07 10:44 Christophe TROESTLER
2004-05-07 11:31 ` John Goerzen
2004-05-07 11:56   ` Richard Jones
2004-05-07 13:56     ` Olivier Grisel
2004-05-07 14:04     ` Gerd Stolpmann
2004-05-07 14:33     ` Christophe TROESTLER
2004-05-07 19:13   ` Evan Martin [this message]
2004-05-07 11:48 ` Nicolas Cannasse
2004-05-07 14:53   ` John Goerzen
2004-05-07 15:07     ` Nicolas Cannasse
2004-05-07 15:40       ` Richard Jones
2004-05-07 15:41         ` Richard Jones
2004-05-07 15:46     ` Gerd Stolpmann
2004-05-07 16:04   ` Paul Snively
2004-05-07 17:55 ` sylvain.le-gall
2004-05-07 18:09 ` N. Owen Gunden
2004-05-07 18:42   ` Benjamin Geer
2004-05-07 19:48     ` Christophe TROESTLER
2004-05-07 20:43 ` Kenneth Knowles
2004-05-08 10:06 ` Stefano Zacchiroli
2004-05-10  7:32 ` Jean-Christophe Filliatre

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=20040507191333.GA522@lulu \
    --to=martine@danga.com \
    --cc=Christophe.Troestler@umh.ac.be \
    --cc=caml-list@inria.fr \
    --cc=jgoerzen@complete.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).