git clone of c17.02 tag on download links page

6 views
Skip to first unread message

Gary Ferland

unread,
Dec 8, 2020, 8:34:20 PM12/8/20
to cloudy-dev
I have been carefully going over the GitLab wiki to confirm that all the links work and that it says what we want.  I came across a problem on the Download Links page.  We give this method of obtaining the c17.02 tag over git:

git clone http://git.nublado.org/cloudy.git -b tags/release/c17.02 --depth 1 c17.02 

This does not address our current GitLab repo and c17 tags are not there.  Are they anywhere?  Should we delete this option?  The other options we give for the download work.

thanks,
Gary

Marios Chatzikos

unread,
Dec 8, 2020, 9:20:57 PM12/8/20
to 'Robin Williams' via cloudy-dev
The tags have not been ported, and will not be recreated, following recent discussions.  I'd say delete it.

--
--
http://groups.google.com/group/cloudy-dev
---
You received this message because you are subscribed to the Google Groups "cloudy-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cloudy-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cloudy-dev/c0f2d360-50c5-4253-99a9-eaa5e6a0f9bdn%40googlegroups.com.

Gary Ferland

unread,
Dec 9, 2020, 2:05:43 PM12/9/20
to cloudy-dev
OK, deleted.  Those tags were a convenience that Robin had set up using a git instance that was set up for this purpose.  I believe you found from the logs the people tended to prefer this.  

When we release C17.03 we can think about what to put on the download links page.  That release will certainly be on git, and not svn, so the page will need some editing.

Marios Chatzikos

unread,
Dec 9, 2020, 3:26:06 PM12/9/20
to 'Robin Williams' via cloudy-dev
We can tag the c17.03 version and use the tag with the download instructions.  The problem with c17.02 is that we did not port the tagged branch, and we do not have the history of the c17_branch to apply a tag to the revision from which .02 was branched from.

Reply all
Reply to author
Forward
0 new messages