From: Jakub Narebski <jnareb@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: git@vger.kernel.org, Timur Tabi <timur@freescale.com>
Subject: [PATCH] gitweb: Document that gitweb deals with bare repositories
Date: Fri, 15 May 2009 23:17:57 +0200 [thread overview]
Message-ID: <20090515211611.27697.82605.stgit@localhost.localdomain> (raw)
In-Reply-To: <ed82fe3e0905151349k15f040aej30dbec82037e9d76@mail.gmail.com>
Add reminders to gitweb/README and gitweb/INSTALL that gitweb works
with bare repositories. While it might be obvious to us, it is not
apparently as evident for newcomers.
Signed-off-by: Jakub Narebski <jnareb@gmail.com>
---
Timur Tabi wrote:
> I noticed that most gitweb pages show their repositories like this:
>
> bluetooth/bluez-gnome.git Bluetooth applications for ... Marcel Holtmann
> bluetooth/bluez-hcidump.git Bluetooth packet analyzer Marcel Holtmann
> bluetooth/bluez.git Bluetooth protocol stack for... Marcel Holtmann
>
> However, mine looks like this:
>
> alsa.1862/.git 8610 audio: fabric driver uses wrong DMA channels for... Timur
> alsa.2598/.git 8610 audio: migrate ASoC V2 drivers to mainline Timur
> alsa.3313/.git Introduce spin_event_timeout() Timur
>
> Notice how my repositories have a trailing "/.git" to them? How do I
> get rid of that?
>
> My gitweb.conf is:
>
> $projectroot = '/home/b04825/git/';
> $site_name = "Timur Tabi's git repositories";
> $home_link = $my_uri;
> @stylesheets = ("gitweb.css");
> $favicon = "git-favicon.png";
> $logo = "git-logo.png";
> $projects_list = '/home/b04825/git/projects_list';
> $projects_list_description_width = 50;
>
> And /home/b04825/git/projects_list looks like:
>
> alsa.1862/.git Timur
> alsa.2598/.git Timur
> alsa.3313/.git Timur
>
> I presume the reason why gitweb shows the trailing "/.git" is because
> that's what my projects_list file contains. However, if I remove the
> "/.git" from projects_list, gitweb can't find any repositories.
Does this explanation help?
gitweb/INSTALL | 14 ++++++++++++++
gitweb/README | 12 +++++++-----
2 files changed, 21 insertions(+), 5 deletions(-)
diff --git a/gitweb/INSTALL b/gitweb/INSTALL
index 18c9ce3..f43e233 100644
--- a/gitweb/INSTALL
+++ b/gitweb/INSTALL
@@ -127,6 +127,20 @@ GITWEB_CONFIG file:
Gitweb repositories
-------------------
+- Gitweb deals with bare repositories, which means that gitweb scans for
+ (in the case where $projects_list is a directory to search for
+ repositories) or has to be provided with list of (in the case where
+ $projects_list is a text file) bare repositories, i.e. $GIT_DIR for
+ each repository. The consequence of that is the fact that if you use
+ gitweb to view non-bare repository named 'repo' then gitweb would show
+ (or would have to be provided with) 'repo/.git'.
+
+ If you want to view a buch of non-bare repositories in gitweb but want
+ them named 'repo.git' as is the standard for bare repositories, you
+ can as a workaround populare $projectroot / $project_list with
+ symbolic links to $GIT_DIR of each project you want to publish (have
+ shown) in gitweb.
+
- By default all git repositories under projectroot are visible and
available to gitweb. The list of projects is generated by default by
scanning the projectroot directory for git repositories (for object
diff --git a/gitweb/README b/gitweb/README
index ccda890..a61fa2f 100644
--- a/gitweb/README
+++ b/gitweb/README
@@ -34,10 +34,11 @@ You can specify the following configuration variables when building GIT:
* GITWEB_LIST
Points to a directory to scan for projects (defaults to project root
if not set / if empty) or to a file with explicit listing of projects
- (together with projects' ownership). See "Generating projects list
- using gitweb" in INSTALL file for gitweb to find out how to generate
- such file from scan of a directory. [No default, which means use root
- directory for projects]
+ (together with projects' ownership). Note that gitweb deals with bare
+ repositories; it shows/uses $GIT_DIR for each repository. See also
+ "Generating projects list using gitweb" in INSTALL file for gitweb to
+ find out how to generate such file from scan of a directory.
+ [No default, which means use root directory for projects]
* GITWEB_EXPORT_OK
Show repository only if this file exists (in repository). Only
effective if this variable evaluates to true. [No default / Not set]
@@ -153,7 +154,8 @@ not include variables usually directly set during build):
Absolute filesystem path which will be prepended to project path;
the path to repository is $projectroot/$project. Set to
$GITWEB_PROJECTROOT during installation. This variable have to be
- set correctly for gitweb to find repositories.
+ set correctly for gitweb to find repositories. (Note that gitweb deals
+ with bare repositories.)
* $projects_list
Source of projects list, either directory to scan, or text file
with list of repositories (in the "<URI-encoded repository path> SP
next prev parent reply other threads:[~2009-05-15 21:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 20:49 Removing the trailing "/.git" from gitweb display? Timur Tabi
2009-05-15 21:14 ` J.H.
2009-05-15 21:17 ` Jakub Narebski [this message]
2009-05-15 21:24 ` [PATCH] gitweb: Document that gitweb deals with bare repositories Timur Tabi
2009-05-15 21:36 ` Jakub Narebski
2009-05-15 22:21 ` Timur Tabi
2009-05-16 2:29 ` Junio C Hamano
2009-05-16 8:14 ` Jakub Narebski
-- strict thread matches above, loose matches on Subject: below --
2008-12-29 20:26 gitweb $export_ok question Thomas Amsler
[not found] ` <6db6bed70812311027g3be1cfbei35c014243237fd59@mail.gmail.com>
2009-01-01 22:51 ` Jakub Narebski
2009-01-03 13:23 ` [PATCH] gitweb: Document that gitweb deals with bare repositories Jakub Narebski
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=20090515211611.27697.82605.stgit@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=timur@freescale.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).