From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: junkio@cox.net
Cc: git@vger.kernel.org
Subject: [PATCH 0/3] git-daemon: plug new upload-tar command
Date: Thu, 31 Aug 2006 14:35:20 +0200 [thread overview]
Message-ID: <11570277231100-git-send-email-vagabon.xyz@gmail.com> (raw)
Here's a simple patchset that basically teach git-daemon about the
upload-tar command added by Junio's commit:
217542640ed219c980fff2b3c307c4520120f20f
With a patched daemon it's now possible to do:
$ git tar-tree --remote=git://host/path/to/repo HEAD > repo.tar
It also creates a 'service' structure to ease future command
integration (like git internal commands handling does). I'm not sure
how usefull it will be, but it improves at least code readability.
Something that may be usefull now is to make git-daemon able to
compress data it sends back...
Franck
---
builtin-tar-tree.c | 2 +
daemon.c | 85 ++++++++++++++++++++++++++++++++++++++++++----------
git.c | 2 +
3 files changed, 71 insertions(+), 18 deletions(-)
next reply other threads:[~2006-08-31 12:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 12:35 Franck Bui-Huu [this message]
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
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=11570277231100-git-send-email-vagabon.xyz@gmail.com \
--to=vagabon.xyz@gmail.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).