From: Jakub Narebski <jnareb@gmail.com>
To: Eugene Sajine <euguess@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: gitweb - bare repos integration - owner info in description file
Date: Sun, 11 Oct 2009 12:39:14 +0200 [thread overview]
Message-ID: <200910111239.15403.jnareb@gmail.com> (raw)
In-Reply-To: <76c5b8580910101845h43a607f0sd4184da302a19963@mail.gmail.com>
On Sun, 11 Oct 2009, Eugene Sajine wrote:
> >
> > The project description, project owner and (clone) url are used by
> > gitweb only, so I don't see why git-clone has to feature-creep to
> > set them.
>
> Well my logic is simple. Gitweb is a part of git bundle. If you don't
> want to use gitweb you're free to use git clone as you want. I don't
> see why not to provide some usability features to it. For me it is
> quite obvious that it will be more comfortable to setup gitweb if this
> would be in place. Instead of putting info in few different places
> manually, why not to give people a possibilty to do that using one
> command?
>
> This is usability feature, but i feel that for me as a person who will
> support big ceantral bare repo hosting server, this would save huge
> time and efforts...
And this would be best left for a custom script creating repositories
and their git hosting related configuration. Such script of necessity
would have to be site-specific, or at least contain site-specific
configuration, like:
* whether to use gitweb.owner or filesystem uid + GECOS is enough
* whether to use gitweb.description or description file
* whether to use gitweb.url, cloneurl file, or let gitweb autogenerate
clone / fetch URL from base URL
* gitosis / gitlite configuration, if needed, or setup of public keys
for SSH authentication
* project README.html file, if used
etc.
git-clone is not a dumping ground (also, code speak louder than words).
I even think it might be mistake to have default 'description' file in
templates...
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2009-10-11 10:41 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 [this message]
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=200910111239.15403.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=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).