From: Petr Baudis <pasky@suse.cz>
To: Eugene Sajine <euguess@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Jakub Narebski <jnareb@gmail.com>,
git@vger.kernel.org
Subject: Re: gitweb - bare repos integration - owner info in description file
Date: Tue, 3 Nov 2009 21:22:11 +0100 [thread overview]
Message-ID: <20091103202211.GA17748@machine.or.cz> (raw)
In-Reply-To: <76c5b8580910121448q67edd935wb189c8a6f9af2f2e@mail.gmail.com>
On Mon, Oct 12, 2009 at 05:48:14PM -0400, Eugene Sajine wrote:
> Hi,
>
> Somebody from development camp recently complained here that there is
> no many end users "chiming" about issues in the mailing list. Well,
> don't tell i didn't try;)
>
> First I tried to use gitweb.url, gitweb.description and gitweb.owner
> files and none of them worked... gitweb is unable to pickup the info
> from those files.
>
> Although it successfully interactively picks up info from description
> and cloneurl files. I didn't find a substitution for gitweb.owner...
>
> I might be sent to RTFM again, but i would like to bring an attention
> to the fact that setting up bare repo with these simplest parameters
> as well as setting up gitweb is a USABILITY NIGHTMARE for beginners. I
> would even say more: while gitweb is very flexible and powerful, all
> its flexibility and power is hidden behind unusable management
> interface, which IMHO requires a lot of improvements . Rebuilding to
> configure? Perl look-and-feel for configuration variables? I think
> this is not the way to configure web applications no matter how smart
> and flexible application should be. There are some problems with XML,
> I don't care. Let's use simple property file. 1 property file! and let
> gitweb read it. don;t like this solution, propose yours..
I think you got confused by perhaps unclear gitweb/README wording. There
is a single property file, it's called "config" and _that's_ where you
set the gitweb configuration variables, in its gitweb section.
Try running
git config gitweb.owner "Eugene Sajine"
git config gitweb.description tralala
within the repository (and optionally marveling at the config file again
afterwards). Is this what you are after?
Perhaps the gitweb/README file doesn't make it clear enough that these
are gitweb configuration variables, not stand-alone files, and maybe it
should provide an example on how to set them. I'm sure that if you will
submit a patch for gitweb/README clarifying this, it will be welcome.
Kind regards,
--
Petr "Pasky" Baudis
A lot of people have my books on their bookshelves.
That's the problem, they need to read them. -- Don Knuth
next prev parent reply other threads:[~2009-11-03 20:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 20:50 gitweb - bare repos integration - owner info in description file Eugene Sajine
2009-10-09 22:07 ` 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 [this message]
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=20091103202211.GA17748@machine.or.cz \
--to=pasky@suse.cz \
--cc=Johannes.Schindelin@gmx.de \
--cc=euguess@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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).