From: Andreas Ericsson <ae@op5.se>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, Carl Baldwin <cnb@fc.hp.com>
Subject: Re: [RFC] Using sticky directories to control access to branches.
Date: Fri, 02 Dec 2005 10:29:21 +0100 [thread overview]
Message-ID: <439013F1.4070600@op5.se> (raw)
In-Reply-To: <7vwtio9u8f.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
>
> It _might_ make sense to have a contrib/examples subdirectory in
> git.git project and keep a collection of examples like this.
>
> Anybody else interested?
>
I am. Ten thousand brains usually do a better job than one in thinking
up cool and nifty stuff. :)
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2005-12-02 9:30 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
2005-12-01 15:42 ` Carl Baldwin
2005-12-02 1:13 ` Junio C Hamano
2005-12-02 9:29 ` Andreas Ericsson [this message]
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=439013F1.4070600@op5.se \
--to=ae@op5.se \
--cc=cnb@fc.hp.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).