Opened 10 years ago
Closed 10 years ago
#12 closed task (fixed)
Establish HTTP redirects for continuity of git services
| Reported by: | mevenson | Owned by: | mevenson |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | component1 | Version: | |
| Keywords: | Cc: | ||
| Parent Tickets: |
Description
Establish HTTP redirects for continuity of git services
Change History (10)
comment:1 Changed 10 years ago by
| Owner: | changed from somebody to mevenson |
|---|---|
| Type: | defect → task |
comment:7 follow-up: 8 Changed 10 years ago by
Subversion and ViewVC URL structures aren't as important as the Git URLs, because on the Subversion/CVS side, there isn't changing much.
comment:8 follow-up: 9 Changed 10 years ago by
Replying to ehuelsmann:
Subversion and ViewVC URL structures aren't as important as the Git URLs, because on the Subversion/CVS side, there isn't changing much.
Agreed. But I'd like a redirect to the equivalent "top-level" in the Git repository, ok?
comment:9 Changed 10 years ago by
Replying to mevenson:
Replying to ehuelsmann:
Subversion and ViewVC URL structures aren't as important as the Git URLs, because on the Subversion/CVS side, there isn't changing much.
Agreed. But I'd like a redirect to the equivalent "top-level" in the Git repository, ok?
Yea. We'd want to point to have a mapping to Git for those CVS projects that are migrated to Git and a mapping to Subversion/Trac?-browser for those projects that are migrated to Subversion.
However, the current step in the planning only involves bringing existing Git projects under control of GitLab?. So, for the short term and GitLab? go-live, we don't need the ViewVC mapping yet. For that, we can use this ticket, but a different set of sub-tasks. So far, I only added the Git/GitLab? related subtasks.
comment:10 Changed 10 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Gitlab listing:
https://common-lisp.net/gitweb/
Subversion and CVS mapping:
https://common-lisp.net/viewvc