git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] gitweb: Document that gitweb deals with bare repositories

From
TTTimur Tabi <timur@freescale.com>
Date
May 15, 2009, 22:21 UTC
Message-ID
<ed82fe3e0905151521m64df542eifca87073c4360fbf@mail.gmail.com>
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
Previous: Jakub NarebskiNext: Junio C Hamano
Message 6 of 8 in “Removing the trailing "/.git" from gitweb display?”
  1. Timur TabiMay 15, 2009
  2. J.H.May 15, 2009
  3. gitweb: Document that gitweb deals with bare repositoriesJakub Narebski, May 15, 2009
  4. Timur TabiMay 15, 2009
  5. Jakub NarebskiMay 15, 2009
  6. Timur TabiMay 15, 2009
  7. Junio C HamanoMay 16, 2009
  8. Jakub NarebskiMay 16, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.