From: Clint Adams <schizo@debian.org>
To: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
Cc: Zsh hackers list <zsh-workers@sunsite.auc.dk>
Subject: Re: sourceforge issues
Date: Mon, 3 Apr 2000 23:23:51 -0400 [thread overview]
Message-ID: <20000403232351.B1658@scowler.net> (raw)
In-Reply-To: <E12cDij-0004C5-00.2000-04-03-21-45-13@mail3.svr.pol.co.uk>; from pws@pwstephenson.fsnet.co.uk on Mon, Apr 03, 2000 at 09:45:11PM +0100
> - Idle question, but does anyone know of an automated way of getting the
> latest version of a file from the CVS archive via the web, without CVS?
> What I mean is, can you tell people to `get the latest version of
> _path_files from <URL_prefix>Completion/Core/_path_files<URL_suffix>'?
> As far as I can see the cvsweb.cgi interface needs you to tell it a
> version number which would put paid to this. The may be some feature
> I haven't seen.
Stock cvsweb checks the revision for the Perl RE /^[\d\.]+$/, so
while CVS will happily take a -r HEAD, cvsweb won't. I assume that
SourceForge's custom version doesn't have this changed.
I see two other groups on our server have their own cvsweb.cgi,
so one might assume that we can put a custom version up ourselves.
Alternately, someone could set up a cronjob to export -r HEAD
to the web dir repeatedly, but that's a bit uglier, IMO.
prev parent reply other threads:[~2000-04-04 3:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-03 20:45 Peter Stephenson
2000-04-03 21:50 ` Adam Spiers
2000-04-04 0:13 ` Bart Schaefer
2000-04-03 21:52 ` Clint Adams
2000-04-04 19:38 ` Peter Stephenson
2000-04-03 22:14 ` Bruce Stephens
2000-04-03 23:00 ` Zefram
2000-04-04 0:09 ` Bart Schaefer
2000-04-04 0:14 ` Chmouel Boudjnah
2000-04-04 19:31 ` Peter Stephenson
2000-04-04 1:27 ` Geoff Wing
2000-04-04 3:23 ` Clint Adams [this message]
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=20000403232351.B1658@scowler.net \
--to=schizo@debian.org \
--cc=pws@pwstephenson.fsnet.co.uk \
--cc=zsh-workers@sunsite.auc.dk \
/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.vuxu.org/mirror/zsh/
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).