| Issue 366: | gerrit gitweb links assume project repositories end in .git | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Affected Version: 2.1 When adding a project, gerrit assumes the git repository on disk is named <project>.git. For our setup this is not true. Also gitweb links will be wrong. This is easy to solve for the project repository (symlink or replicate would work fine), but have not found a solution that works for other places where it appends .git without source changes.
Dec 22, 2009
#1
sop@google.com
Dec 22, 2009
Hi, Yeah, I am aware of the convention. When we setup our ssh based git we chose ssh://git.<domain>/git/<project> as repo URLs, we stripped out .git because it would be a lot of git in the name :) You are right, project git repository works fine without the suffix. That only leaves the gitweb links AFAIK.
Dec 24, 2009
Oh, yea, gitweb URLs do just slap on .git suffix without considering whether or not that is correct for the receiving gitweb instance. So I guess this bug is really just about gitweb URLs being wrong.
Summary:
gerrit gitweb links assume project repositories end in .git
Status: Accepted
Dec 28, 2009
issue 371 makes gitweb configurable, which means a custom gitweb configuration could be used for your installation.
Blockedon:
371
Dec 29, 2009
In 2.1.1 you can now add to your gerrit.config:
[gitweb]
url = ...
project = ?p=${project};a=summary
revision = ?p=${project};a=commit;h=${commit}
branch = ?p=${project};a=shortlog;h=${branch}
To use gitweb.cgi, but without the .git suffix on project names.
Status:
Fixed
Labels: FixedIn-2.1.1
Jan 10, 2010
Works like a charm. Thanks.
Oct 21, 2012
(No comment was entered for this change.)
Status:
Released
Blockedon: -gerrit:371 gerrit:371 |
|
| ► Sign in to add a comment |