From: Junio C Hamano <junkio@cox.net>
To: Carl Baldwin <cnb@fc.hp.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Using sticky directories to control access to branches.
Date: Mon, 21 Nov 2005 11:29:12 -0800 [thread overview]
Message-ID: <7vacfxsstz.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20051121180133.GA28171@hpsvcnb.fc.hp.com> (Carl Baldwin's message of "Mon, 21 Nov 2005 11:01:33 -0700")
Carl Baldwin <cnb@fc.hp.com> writes:
> To follow-up on this. Here is a final version of this script that was
> started by Junio. I polished it and made it work the way I want it.
> Hopefully, someone on the list will find it useful.
Looking good. We might want to have collections of user
contributed hooks, maybe a new directory examples/ perhaps?
next prev parent reply other threads:[~2005-11-21 19:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 17:01 [RFC] Using sticky directories to control access to branches Carl Baldwin
2005-11-18 7:55 ` Junio C Hamano
2005-11-21 18:01 ` Carl Baldwin
2005-11-21 19:29 ` Junio C Hamano [this message]
2005-12-01 15:42 ` Carl Baldwin
2005-12-02 1:13 ` Junio C Hamano
2005-12-02 9:29 ` Andreas Ericsson
2005-12-02 9:35 ` Junio C Hamano
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=7vacfxsstz.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=cnb@fc.hp.com \
--cc=git@vger.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).