Add a New Comment (Rich Markup)
Comment Type & Canned Response: None None > Multiple Canned Responses Mailing-list created This will be fixed in the near future. Wrong support: not a project Known issue: will be fixed soon No Response
( Jump to the original submission )
ok, closing. feel free to re-open if problems persist.
Thanks Karl, that is a big improvement.
Thanks Glenn. It actually wasn't clear to me before whether emacs-bzr-repository was a specially chosen name or just generic.
I made the changes and pushed them live, please check again.
(savannah administrators: instructions for pushing such content changes live are now at http://savannah.gnu.org/maintenance/SavaneConfiguration)
> Sylvain has updated the live savannah. Please review...
Thanks. There is still a typo in the example scp command, as pointed out in sr #107118 comment #2. "emacs-bzr-repository" should only appear once, not twice.
Also it would probably be better to use a generic name like "my-repository", since it looks odd to see "emacs-bzr-repository" in eg the gsl instructions.
Sylvain has updated the live savannah. Please review (for example) http://savannah.gnu.org/bzr/?group=gsl ...
Well, I'm not sure I should have, but I checked in a new version of the relevant template file (attached). I think a cron job and/or Sylvain may have to push it to the live site, though. I could easily have made a mistake among the changes since I can't test it.
I also tried to incorporate the developer changes from 107118. Thanks for pointing that out, Glenn.
For those who have access to savannah web CVS (KarlF?), the file I edited was administration/content/gnu-content/bzr/index.txt.
I was under the impression that KarlF and others were hoping to revamp bzr support in general ... hope this helps.
(file #20686)
This is the same issue as reported 6 months ago in sr #107118. I hope you have more luck in getting a response from Savannah.
As noted on the bzr page for each project, the example bzr branch url given there is not valid if the project uses a different layout.
I think the text could give an additional example on what to do then.
I've attached an alternative text as an HTML file and text version below (replace FOO by the project name) - it tells people they can look in the directory to see the branches.
===Original===
Anonymous read-only access
bzr branch http://bzr.savannah.gnu.org/r/gsl
Note: these paths are the default paths. Maybe the project is using a different layout.
===Suggested===
The Bzr repositories for projects use separate directories for each branch.
You can see the branch names in the repository by pointing your web browser at http://bzr.savannah.gnu.org/r/FOO/
For a repository with only a top-level .bzr directory use
bzr branch http://bzr.savannah.gnu.org/r/FOO
For a repository with separate branch directories (e.g trunk, devel, etc) use
bzr branch http://bzr.savannah.gnu.org/r/FOO/<branch>
where <branch> is the name of the branch you want.
(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)
Attach Files: Comment:
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Only logged-in users can vote.
Please enter the title of George Orwell's famous dystopian book (it's a date):
Follow 6 latest changes.
Copyright © 2023 Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team. Source Code
Powered by Savane 3.10