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 17:21:42 -0500 [thread overview]
Message-ID: <ed82fe3e0905151521m64df542eifca87073c4360fbf@mail.gmail.com> (raw)
In-Reply-To: <200905152336.49319.jnareb@gmail.com>
On Fri, May 15, 2009 at 4:36 PM, Jakub Narebski <jnareb@gmail.com> wrote:
> Gitweb can deal with non-bare repositories. It is only that because
> gitweb is not interested in working area, it shows $GIT_DIR (path to
> repository itself) as name/path to repository. Therefore repo/.git
> for non-bare repositories, because it is repository itself that matters.
I understand that, but why does gitweb have to punish me because I
give it more than it cares about?
> If you provide access for others, i.e. if those repositories shown in
> gitweb are public repositories, it is much better to use bare
> repositories for that.
Why? What difference does it make if they clone directly from my
working tree, instead of some shadow repository?
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2009-05-15 22:21 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
2009-05-15 21:36 ` Jakub Narebski
2009-05-15 22:21 ` Timur Tabi [this message]
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=ed82fe3e0905151521m64df542eifca87073c4360fbf@mail.gmail.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 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).