git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Petr Baudis <pasky@suse.cz>, Luben Tuikov <ltuikov@yahoo.com>,
	"J.H." <warthog9@kernel.org>, git <git@vger.kernel.org>,
	Sylvain Rabot <sylvain@abstraction.fr>
Subject: Re: Make Gitweb behave like Apache mod_userdir
Date: Tue, 17 Nov 2009 14:58:55 +0100	[thread overview]
Message-ID: <200911171458.56047.jnareb@gmail.com> (raw)
In-Reply-To: <7vskcffqkn.fsf@alter.siamese.dyndns.org>

On Sun, 15 Nov 2009, Junio C Hamano wrote:
> Sylvain Rabot <sylvain@abstraction.fr> writes:
> 
> > I made gitweb behave a bit like UserDir module will in apache.
> > In fact it's only configuration but I think it could be useful to others.
> 
> Thanks.  Any comment from gitweb gangs?

I would respond earlier if it was submitted with patch inline in mail
body, and not attached.  If it needs to be attached (because of MUA/MTA
linewrapping or encoding issues), it should use 8bit and not base64
content transfer encoding, have 'text/plain' and not 
'application/octet-stream' content type, and "inline" and not "attachement"
in content disposition.

It also lacks proper commit message (although email describes it quite
well) and signoff, as per Documentation/SubmittingPatches.

I like this patch.  More examples in gitweb/README are always good idea.

> > Basicly it allows users of your server who use git to be able to use

"Basically"

> > gitweb to browse their own root project. E.G. :

"For example"

> >
> > Alice's private repos :
> >
> > /home/alice/git/product_a.git (cloned from /var/git/product_a.git)
> > /home/alice/git/product_b.git (cloned from /var/git/product_b.git)
> > /home/alice/git/product_c.git (cloned from /var/git/product_c.git)
> >
> > Alice's links to her repos which she wants to be able to browse with gitweb :

"Alice links", or "Alice creates symbolic links"

> >
> > /home/alice/gitweb/product_a -> /home/alice/git/product_a.git/.git
> > /home/alice/gitweb/product_c -> /home/alice/git/product_c.git/.git
> >
> > Bare repos :
> >
> > /var/git/product_a.git
> > /var/git/product_b.git
> > /var/git/product_c.git
> > /var/git/product_d.git

The description is a bit lacking.  Where user should put theirs git
repositories, or symbolic links to git repositories?  How it would
look like in gitweb?

-- 
Jakub Narebski
Poland

  reply	other threads:[~2009-11-17 13:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-15 10:04 Make Gitweb behave like Apache mod_userdir Sylvain Rabot
2009-11-15 21:03 ` Junio C Hamano
2009-11-17 13:58   ` Jakub Narebski [this message]
2009-11-17 15:51     ` Sylvain Rabot
2009-11-17 18:12       ` Jakub Narebski
2009-11-17 19:56         ` Sylvain Rabot
2009-11-17 20:15 ` Junio C Hamano
2009-11-17 20:24   ` Sylvain Rabot
2009-11-17 22:10     ` Junio C Hamano
2009-11-17 22:54       ` Sylvain Rabot
2009-11-17 23:40         ` Junio C Hamano
2009-11-17 23:52           ` J.H.
2009-11-17 22:59       ` J.H.
2009-11-17 23:46         ` Junio C Hamano
2009-11-17 23:59           ` J.H.
2009-11-18  0:14             ` Junio C Hamano
2009-11-18  0:00           ` J.H.
2009-11-18  0:16         ` Sylvain Rabot

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=200911171458.56047.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=ltuikov@yahoo.com \
    --cc=pasky@suse.cz \
    --cc=sylvain@abstraction.fr \
    --cc=warthog9@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).