From: Sitaram Chamarty <sitaramc@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Jakub Narebski <jnareb@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Tommi Virtanen <tv@eagain.net>
Subject: Re: gitosis-lite
Date: Tue, 25 Aug 2009 08:30:26 +0530 [thread overview]
Message-ID: <2e24e5b90908242000t212347fbkec6a01396d784736@mail.gmail.com> (raw)
In-Reply-To: <20090824151051.GB1033@spearce.org>
On Mon, Aug 24, 2009 at 8:40 PM, Shawn O. Pearce<spearce@spearce.org> wrote:
> Sitaram Chamarty <sitaramc@gmail.com> wrote:
>> I'll be honest: I
>> came away feeling very stupid after trying to read and
>> understand that program. It was... humbling :(
> *sigh* That's not good, the hook is meant as a practical example,
> if it was too complex to understand, I did a poor job of writing it.
Hmmm no. It was just doing too much to grasp in one
reading, especially by someone whose perl seems to have
rusted a wee bit, if you've seen Jakub's reply :)
I took a slightly longer look after your mail and I grokked
it a lot better. And wow... I guess you called it
"paranoid" for a reason :-)
In the environments I'm catering to, every commit will be
reviewed by someone else (usually someone more experienced,
and having a bigger picture), so "you're not allowed to
touch this file" type of thing will all come out.
All I need is to make sure the important branches can only
be pushed to by certain people; the "process" will take care
of the rest.
next prev parent reply other threads:[~2009-08-25 3:00 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 ` gitosis-lite Jakub Narebski
2009-08-24 14:35 ` gitosis-lite Sitaram Chamarty
2009-08-24 15:10 ` gitosis-lite Shawn O. Pearce
2009-08-25 3:00 ` Sitaram Chamarty [this message]
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=2e24e5b90908242000t212347fbkec6a01396d784736@mail.gmail.com \
--to=sitaramc@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=spearce@spearce.org \
--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 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).