From: Jakub Narebski <jnareb@gmail.com>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>, Tommi Virtanen <tv@eagain.net>
Subject: Re: gitosis-lite
Date: Mon, 24 Aug 2009 06:13:53 -0700 (PDT) [thread overview]
Message-ID: <m3ab1pmk1c.fsf@localhost.localdomain> (raw)
In-Reply-To: <2e24e5b90908240528v56fdf30cq4c046fca321a3b17@mail.gmail.com>
Sitaram Chamarty <sitaramc@gmail.com> writes:
> Hello all,
>
> I created a new project called gitosis-lite, which combines
> the essential pieces of gitosis with the per-branch
> permissions stuff in the example in the howto directory of
> git.git.
>
> The config file is different, (there's an annotated example
> you can look at).
>
> The "why" and the "what" are all at
> http://github.com/sitaramc/gitosis-lite
Could you add information about this tool (perhaps after confirmation
/ deciding on project name[1]) to Git Wiki page
http://git.or.cz/gitwiki/InterfacesFrontendsAndTools
somewhere below Gitosis? Please do not forget to include that it is
written in Perl; see other entries for example.
You wrote in project's README.markdown that you were inspired by
Gitosis (which requires Python and python-setuptools) and
Documentation/howto/update-hook-example.txt (which uses bash).
Why not contrib/hooks/update-paranoid (which is written in Perl)?
Using Perl code for configuration is simple and fast, but not very
secure. Why not use git config format (via "git config -l -z" like in
gitweb), or YAML or JSON (or Storable)? Well, YAML might be overkill.
BTW. if you blog about gitosis-lite (http://sitaramc.blogspot.com/)
it could be picked up by Perl Iron Man Blogging challenge, and you
could get wider review.
[1]: gitosis-lite doesn't look like CPAN-y name. Git::Admin perlhaps?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-08-24 13:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 12:28 gitosis-lite Sitaram Chamarty
2009-08-24 13:13 ` Jakub Narebski [this message]
2009-08-24 14:35 ` gitosis-lite Sitaram Chamarty
2009-08-24 15:10 ` gitosis-lite Shawn O. Pearce
2009-08-25 3:00 ` gitosis-lite Sitaram Chamarty
2009-08-24 15:43 ` gitosis-lite Jakub Narebski
2009-08-24 18:44 ` gitosis-lite Jakub Narebski
2009-08-25 5:53 ` gitosis-lite Sitaram Chamarty
2009-08-25 12:05 ` gitosis-lite Jakub Narebski
2009-08-26 5:01 ` gitosis-lite Sitaram Chamarty
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=m3ab1pmk1c.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=sitaramc@gmail.com \
--cc=tv@eagain.net \
/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.