Re: Enhancements to git-protocoll
- From
Fredrik Gustafsson <iveqy@iveqy.com>
- Date
- Jul 29, 2012, 21:26 UTC
- Message-ID
- <20120729212627.GA26430@paksenarrion.iveqy.com>
- In-Reply-To
- <7vvch6uw89.fsf@alter.siamese.dyndns.org>
Sorry I missed this thread earlier. I'll drop this if it's not something that's wanted.
On Sun, Jul 29, 2012 at 01:51:34PM -0700, Junio C Hamano wrote:
Show 5 quoted lines
> Sitaram Chamarty <sitaramc@gmail.com> writes: > > > Uggh, no. Client-git should only talk to server-git. It shouldn't be > > talking first to some *other* program (in this case gitolite), and > > then to to server-git. That doesn't sound sane to me.
This is exactly the way gitolite works. It's placed between git-server and git-client. Does some checks and approves a connection if some criterias isn't met. See the example when trying to clone an non-existing repo from gitolite. You won't get an git error but a gitolite error.
I can understand why my idea is beeing rejected but I can't see why the gitolite way should be considered sane. It seems more like an hack to me (according to git design principles).
So from a git point of view, why is it sane for passing through STDERR but not STDIN and STDOUT?
(I realize that this is a closed matter but would appriciate an explanation solely for my own educational purpose).
-- Med vänliga hälsningar Fredrik Gustafsson tel: 0733-608274 e-post: iveqy@iveqy.com