From: Junio C Hamano <junkio@cox.net>
To: Jason McMullan <jason.mcmullan@timesys.com>
Cc: git@vger.kernel.org
Subject: Re: Last mile for 1.0
Date: Sun, 05 Jun 2005 16:45:54 -0700 [thread overview]
Message-ID: <7vzmu4weod.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7vk6l8xue5.fsf_-_@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Sun, 05 Jun 2005 16:21:06 -0700")
I did not mention git-sync by Jason McMullan on my list of "what
I want to have in 1.0", but that was not because I object to the
idea of having a sync mechanism that knows and takes advantage
of how GIT works. Quite the contrary.
I would like to see such a GIT specific smart sync mechanism
some day. git-http-pull lets us use a dumb server and cannot
assume server-side smarts, git-local-pull operates in an
environment where latency does not matter, but git-ssh-pull and
git-sync are solutions for the real network environment where
latency matters, and having a smart sync mechanism is a big win.
I just do not feel, judging from its current protocol command
set, it offers enough improvements over what git-ssh-push/pull
pairs already give us; I'd be happy to be corrected, of course,
if this is a misconception.
next prev parent reply other threads:[~2005-06-05 23:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-05 21:39 [PATCH] Documentation: describe git extended diff headers Junio C Hamano
2005-06-05 22:11 ` Linus Torvalds
2005-06-05 22:25 ` [PATCH] Fix diff.c to match rename extended header to the document Junio C Hamano
2005-06-05 22:27 ` [PATCH] Fix apply.c " Junio C Hamano
2005-06-05 22:33 ` Linus Torvalds
2005-06-05 23:21 ` Last mile for 1.0 Junio C Hamano
2005-06-05 23:45 ` Junio C Hamano [this message]
2005-06-06 13:29 ` McMullan, Jason
2005-06-06 0:02 ` Linus Torvalds
2005-06-06 0:46 ` [PATCH] git-whatchanged vs "cvs annotate" Junio C Hamano
2005-06-06 5:43 ` Last mile for 1.0 Thomas Glanzmann
2005-06-06 6:13 ` Linus Torvalds
2005-06-06 6:35 ` Junio C Hamano
2005-06-06 6:44 ` Linus Torvalds
2005-06-06 6:44 ` Thomas Glanzmann
2005-06-06 6:57 ` Linus Torvalds
2005-06-06 7:01 ` Thomas Glanzmann
2005-06-06 7:05 ` Junio C Hamano
2005-06-06 14:37 ` Linus Torvalds
[not found] ` <7vy89ns354.fsf_-_@assigned-by-dhcp.cox.net>
[not found] ` <Pine.LNX.4.58.0506061312520.1876@ppc970.osdl.org>
[not found] ` <Pine.LNX.4.58.0506061403170.1876@ppc970.osdl.org>
[not found] ` <7vekbfnot9.fsf@assigned-by-dhcp.cox.net>
[not found] ` <Pine.LNX.4.58.0506061453400.1876@ppc970.osdl.org>
[not found] ` <7vy89mlmsv.fsf_-_@assigned-by-dhcp.cox.net>
[not found] ` <7vis0qk2jo.fsf_-_@assigned-by-dhcp.cox.net>
[not found] ` <Pine.LNX.4.58.0506070808180.2286@ppc970.osdl.org>
2005-06-08 3:53 ` 3-way read-tree case matrix Junio C Hamano
2005-06-08 5:32 ` Junio C Hamano
2005-06-08 9:08 ` [PATCH] Tests: read-tree -m test updates Junio C Hamano
2005-06-06 6:45 ` Last mile for 1.0 Junio C Hamano
2005-06-06 7:03 ` Linus Torvalds
[not found] ` <7vacm4ufnl.fsf@assigned-by-dhcp.cox.net>
2005-06-06 14:47 ` Linus Torvalds
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=7vzmu4weod.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=jason.mcmullan@timesys.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