Open GoogleCodeExporter opened 8 years ago
It's on this page btw, http://code.google.com/p/blueprintcss/source
Original comment by stech...@gmail.com
on 15 Oct 2007 at 5:32
The page you referenced is managed by google code and we do not control its
content
as far as I am aware (although we should be able to as not all projects follow
the
strict trunk/branches/tags dirs right in the root).
You are correct in noting that the SVN checkout URL provided is incorrect for
this
project since it was setup with sub-project sub-dirs (one of which is
blueprint) and
we don't have the typical trunk/tags/branches at the root.
Olav, can you please modify the wiki page here, and any references on your
blog, to
point to one of the following two SVN commands to checkout blueprint.
Check Out Only Blueprint core code:
--
svn checkout http://blueprintcss.googlecode.com/svn/blueprint/trunk/blueprint
blueprintcss
Or Check Out Entire repository and related sub-projects:
--
svn checkout http://blueprintcss.googlecode.com/svn blueprintcss
Glenn
Original comment by glenn.re...@gmail.com
on 16 Oct 2007 at 7:24
Yeah, I was thinking that. Cool--I hope this helps others who try to search for
it =)
Original comment by stech...@gmail.com
on 16 Oct 2007 at 7:33
Yeah, it's too bad we can't change what it says on the main source page. It
really should be dynamic, or at least
a preference. Strange really, as Google Code seems to allow lots of
customizations on similar issues.
Original comment by ola...@gmail.com
on 13 Jan 2008 at 5:42
Google Code use this SVN structure:
wiki
project
branches
tags
trunk
As you can see, the link is wrong, but I don't think there's any way to change
the link.
We could do something like this:
branches
tags
trunk
wiki
But I'm not sure this would be a valid SVN structure..
Original comment by ola...@gmail.com
on 18 Feb 2008 at 7:54
Since there doesn't seem to be any subprojects, maybe svn mv things around so
they match Google's standards
would be in order; though this may break existing checkouts.
Original comment by m...@pixelcort.com
on 6 Jun 2008 at 11:04
Mmm, you could try emailing Google to have them change this to be a dynamic
feature.
Google is pretty good about these kinds of things and would most likely conform.
Original comment by Tig...@gmail.com
on 24 Jun 2008 at 9:21
Original issue reported on code.google.com by
stech...@gmail.com
on 15 Oct 2007 at 5:32