Eugene Sajine <euguess@xxxxxxxxx> writes:
> Here is another issue with gitweb integration which i think might be
> considered as a feature proposal:
>
> I have a central place where bare repos are. They're owned by the user
> under which we are serving them, let's say “git”. So, gitweb is going
> to show me
>
> Repo1 owner git etc…
>
> In order to show a real owner I have to rebuild gitweb.cgi, to tell it
> to use the file for GITWEB_LIST and edit the file… In fact I think
> gitweb shouldn’t carry this info, but bare repos should.
It is not gitweb that carries this info, but file with list of
repositories (GITWEB_LIST). And you can pre-generate this file using
gitweb.
>
> So my idea is:
>
> Either provide a key to
> $ git clone –bare –u “owner/email”
>
> or take the user.email parameter from .gitconfig.
>
> in both cases the info can go to description file of bare repo, so it
> can look like:
>
> $owner=owner@xxxxxxxxxx
>
> $description=”very long description”
RTFM (in this case gitweb/README). gitweb.owner and gitweb.description
configuration variables in per-repository config.
>
> Or in xml form…
Aaaaaaaaaaaaaaaaaaaaaaaa...
%
"To be fair, there are uses for XML. On Halloween, for example."
- Johannes Schindelin, on git@xxxxxxxxxxxxxxx
%
>
>
> Yes, description file might become a bit more complicated in its
> layout. But, the benefits are obvious:
>
> - No need to support multiple lists/files
> - Bare repo carries all info about itself (together with –d feature I
> described earlier).
>
> I this circumstances gitweb’s GITWEB_LIST will be only filter (only
> repo path is necessary to show/not show), and it seems that narrowed
> functionality here is a good thing...
GITWEB_LIST is meant for the case when you want to avoid scanning
filesystem for git repositories. And you can filter out repositories
without using GITWEB_LIST (see documentation).
--
Jakub Narebski
Poland
ShadeHawk on #git
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html