From: Timur Tabi <timur@freescale.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: Document that gitweb deals with bare repositories
Date: Fri, 15 May 2009 16:24:36 -0500 [thread overview]
Message-ID: <4A0DDD94.1010901@freescale.com> (raw)
In-Reply-To: <20090515211611.27697.82605.stgit@localhost.localdomain>
Jakub Narebski wrote:
> Does this explanation help?
Yes, it does, but I wish it weren't true. I don't see why gitweb can't be enhanced to support non-bare repositories without using symlinks or other hackery.
To avoid the overhead of gitweb scanning all of my repositories for other respitories, I use a packages_list, which is automatically recreated whenever I add a new repo. However, I think having to create a shadow bare repository with a cron job to keep it more-or-less update is wrong.
Just my two cents.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2009-05-15 21:24 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 ` [PATCH] gitweb: Document that gitweb deals with bare repositories Jakub Narebski
2009-05-15 21:24 ` Timur Tabi [this message]
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=4A0DDD94.1010901@freescale.com \
--to=timur@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.