From: Eugene Sajine <euguess@gmail.com>
To: git@vger.kernel.org
Subject: gitweb - bare repos integration - owner info in description file
Date: Fri, 9 Oct 2009 16:50:00 -0400 [thread overview]
Message-ID: <76c5b8580910091350o5cd90d3dobe2a21c18fa56dfd@mail.gmail.com> (raw)
Hi,
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.
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@server.com
$description=”very long description”
Or in xml form…
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...
Your thoughts?
Thanks,
Eugene
next reply other threads:[~2009-10-09 20:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 20:50 Eugene Sajine [this message]
2009-10-09 22:07 ` gitweb - bare repos integration - owner info in description file Jakub Narebski
2009-10-09 22:32 ` Eugene Sajine
2009-10-10 18:45 ` Jakub Narebski
2009-10-11 1:45 ` Eugene Sajine
2009-10-11 10:39 ` Jakub Narebski
2009-10-12 0:04 ` Johannes Schindelin
2009-10-12 21:48 ` Eugene Sajine
2009-10-12 23:19 ` Miklos Vajna
2009-11-03 20:22 ` Petr Baudis
2009-11-04 23:48 ` Eugene Sajine
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=76c5b8580910091350o5cd90d3dobe2a21c18fa56dfd@mail.gmail.com \
--to=euguess@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).