Updates:
Status: Verified
Comment #10 on issue 1244 by v.villenave: Change to the new website
http://code.google.com/p/lilypond/issues/detail?id=1244
Closing. See issue 1272 et al. for follow-up.
___
bug-lilypond mailing list
bug-lilypond@gnu
- Original Message -
From: "Phil Holmes"
To:
Sent: Friday, September 24, 2010 6:45 PM
Subject: Re: Issue 1244 in lilypond: Change to the new website
"Trevor Daniels" wrote in message
news:e3a27db9e1c44b78b6c8106695ee5...@trevorlaptop...
Graham
Comment
"Trevor Daniels" wrote in message
news:e3a27db9e1c44b78b6c8106695ee5...@trevorlaptop...
Graham
Comment #8 on issue 1244 by percival.music.ca: Change to the new website
http://code.google.com/p/lilypond/issues/detail?id=1244
To comment 3 and 5, Trevor:
Aye, that be a good thing. Too many we
Graham
Comment #8 on issue 1244 by percival.music.ca: Change to the new
website
http://code.google.com/p/lilypond/issues/detail?id=1244
To comment 3 and 5, Trevor:
Aye, that be a good thing. Too many weens be getting themselves
in trouble by stumbling across 2.13 without intending to.
(so
Updates:
Status: Fixed
Comment #9 on issue 1244 by percival.music.ca: Change to the new website
http://code.google.com/p/lilypond/issues/detail?id=1244
I believe that everything here is fixed. Note that we are (finally!) using
the .htaccess that's in git:
Documentation/web/server/l
Comment #8 on issue 1244 by percival.music.ca: Change to the new website
http://code.google.com/p/lilypond/issues/detail?id=1244
To comment 3 and 5, Trevor:
Aye, that be a good thing. Too many weens be getting themselves in trouble
by stumbling across 2.13 without intending to.
(sorry, I'm q
Comment #7 on issue 1244 by percival.music.ca: Change to the new website
http://code.google.com/p/lilypond/issues/detail?id=1244
To comment 6, Valentin: as mentioned in:
Documentation/web/server/lilypond.org.htaccess
the /documentation => /doc redirect breaks the doc index with the old
site
Updates:
Status: Started
Owner: percival.music.ca
Comment #6 on issue 1244 by v.villenave: Change to the new website
http://code.google.com/p/lilypond/issues/detail?id=1244
As I said earlier, I think we should add a few redirects to keep at least
the following URLs working:
ht
Comment #5 on issue 1244 by tdanielsmusic: Change to the new website
http://code.google.com/p/lilypond/issues/detail?id=1244
No, these clearly refer to the stable release, although extra clarity
wouldn't harm; I meant the horizontal menu right at the top -
Introduction/Download/Manuals/Comm
Comment #4 on issue 1244 by percival.music.ca: Change to the new website
http://code.google.com/p/lilypond/issues/detail?id=1244
By "the top-level menu", do you mean the box that says "Note: these are
unstable development... we urge you to use the stable _Download_, and read
the stable _manu
Comment #3 on issue 1244 by tdanielsmusic: Change to the new website
http://code.google.com/p/lilypond/issues/detail?id=1244
On the development page, http://lilypond.org/development.html, if I want to
download the latest development version for Windows there are two
potentially promising cli
Comment #2 on issue 1244 by percival.music.ca: Change to the new website
http://code.google.com/p/lilypond/issues/detail?id=1244
New website is "live" now. At first glance, I think I've done everything,
but I'm not marking this fixed yet because I want to double-check when I'm
more alert.
Comment #1 on issue 1244 by PhilEHolmes: Change to the new website
http://code.google.com/p/lilypond/issues/detail?id=1244
In short, one of the changes is that, for the "stable" site (to be
2.14) "Back to documentation index" should point to /website/manuals.html
___
Status: Accepted
Owner:
Labels: Type-Build Priority-Critical website
New issue 1244 by percival.music.ca: Change to the new website
http://code.google.com/p/lilypond/issues/detail?id=1244
A few items can only be done once we finally change over. This is planned
to happen with the first "
14 matches
Mail list logo
