From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Version Numbers in Download File Names
Date: Wed, 12 Jul 2006 15:18:42 +0200 [thread overview]
Message-ID: <44B4F6B2.8070702@elvenkind.com> (raw)
In-Reply-To: <44B4ED0E.1040104@tttech.com>
Matthias Wächter wrote:
>
> Two comments nevertheless.
>
> https://foundry.supelec.fr/frs/?group_id=14 gives me quite some versions of
> Context, but the download paths for each precise version is not related to the
> release date or the SVN revision,
Correct. SVN release ids have numbers, not dates, and it was a bitch
getting all this stuff into subversion as it was, so I did not want
to fiddle too much with extra tag ids. The SVN log entry is always the
release date number.
For the 'Files' section, it could actually be retrofitted, by
rearranging the uploaded files (and uploading a few hundred
extra zip files that are now skipped). I will happily give
anybody who wants to do such a project enough gforge permissions
to do so ;-)
> Second: I tried to checkout the repository anonymously as mentioned
> on https://foundry.supelec.fr/scm/?group_id=14 without success
That is odd, because it should have worked. I will investigate
Greetings, Taco
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2006-07-12 13:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 11:20 Matthias Wächter
2006-07-12 11:51 ` Taco Hoekwater
2006-07-12 12:37 ` Matthias Wächter
2006-07-12 13:18 ` Taco Hoekwater [this message]
2006-07-12 16:04 ` Matthias Wächter
2006-07-12 17:27 ` Taco Hoekwater
2006-07-13 14:26 ` Hans Hagen
2006-07-13 13:37 ` Hans Hagen
2006-07-12 13:01 ` Hans Hagen
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=44B4F6B2.8070702@elvenkind.com \
--to=taco@elvenkind.com \
--cc=ntg-context@ntg.nl \
/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).