From: Junio C Hamano <junkio@cox.net>
To: "Franck Bui-Huu" <vagabon.xyz@gmail.com>
Cc: "Rene Scharfe" <rene.scharfe@lsrfire.ath.cx>,
junkio@cox.net, git@vger.kernel.org
Subject: Re: [PATCH 0/3] git-daemon: plug new upload-tar command
Date: Sat, 02 Sep 2006 03:32:04 -0700 [thread overview]
Message-ID: <7vfyfa1rvf.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <cda58cb80609020114h1e1ee553saf5aa90df8bc3ba0@mail.gmail.com> (Franck Bui-Huu's message of "Sat, 2 Sep 2006 10:14:50 +0200")
"Franck Bui-Huu" <vagabon.xyz@gmail.com> writes:
>> So if you beat me to it, that would be great. Or if you have a better
>> idea, that would be also great. :-)
>
> Well I'll try to start something, not sure to have a lot of time
> though. Please contact me before starting anything, I would be sad to
> write something for /dev/null again ;)
I do not necessarily think your effort were for /dev/null; for
example, I was hoping you defend [PATCH 3/3].
While it makes sense to make "tar-tree --remote" usable outside
a git managed repository, I think people expect the connection
to obey core.gitproxy if the command is run inside a repository
that has a configuration file.
next prev parent reply other threads:[~2006-09-02 10:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 12:35 [PATCH 0/3] git-daemon: plug new upload-tar command Franck Bui-Huu
2006-08-31 12:35 ` [PATCH 1/3] daemon.c: introduce daemon's service Franck Bui-Huu
2006-08-31 13:07 ` Franck Bui-Huu
2006-08-31 15:15 ` [PATCH 1/3] daemon.c: introduce daemon's service [take #2] Franck Bui-Huu
2006-08-31 12:35 ` [PATCH 2/3] daemon.c: added upload-tar service Franck Bui-Huu
2006-08-31 12:35 ` [PATCH 3/3] git-tar-tree.c: no need to be in a git repo when using --remote Franck Bui-Huu
2006-08-31 17:45 ` [PATCH 0/3] git-daemon: plug new upload-tar command Rene Scharfe
2006-09-02 8:14 ` Franck Bui-Huu
2006-09-02 10:32 ` Junio C Hamano [this message]
2006-09-02 10:36 ` Jakub Narebski
2006-09-02 20:12 ` Franck Bui-Huu
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=7vfyfa1rvf.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=rene.scharfe@lsrfire.ath.cx \
--cc=vagabon.xyz@gmail.com \
/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).