From: "McMullan, Jason" <jason.mcmullan@timesys.com>
To: "Linus Torvalds" <torvalds@osdl.org>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: [PATCH] git-daemon server
Date: Fri, 03 Jun 2005 12:09:41 -0400
Date: Fri, 3 Jun 2005 12:02:51 -0400 [thread overview]
Message-ID: <1117814982.32257.64.camel@jmcmullan.timesys> (raw)
In-Reply-To: <Pine.LNX.4.58.0506030856490.1876@ppc970.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
On Fri, 2005-06-03 at 09:02 -0700, Linus Torvalds wrote:
> ie it wouldn't be a deamon at all, it would be a foreground server. So I'd
> call it just "git-server" or something.
Server.. Sounds ok. Will do.
> Anyway, technically this looks ok, but I'd hate to apply it until there is
> something that actually uses it and an example of that usage.
Well, I use it to keep my home and work repos in sync, but yeah,
users == 1 doesn't make a good case for inclusion.
I just want to have this out there, because I find rsync a little too
heavy handed for my taste, and I'm still hesitant about the cg-rpush
locking semantics.
--
Jason McMullan <jason.mcmullan@timesys.com>
TimeSys Corporation
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-03 16:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 15:22 [PATCH] git-daemon server Jason McMullan
2005-06-03 16:02 ` Linus Torvalds
2005-06-03 16:09 ` McMullan, Jason [this message]
2005-06-03 16:30 ` Linus Torvalds
2005-06-03 17:18 ` McMullan, Jason
2005-06-03 17:41 ` Linus Torvalds
2005-06-03 19:30 ` McMullan, Jason
2005-06-03 20:25 ` Linus Torvalds
2005-06-03 20:56 ` McMullan, Jason
2005-06-03 21:38 ` Linus Torvalds
2005-06-03 22:01 ` Daniel Serpell
2005-06-05 16:44 ` Jason McMullan
2005-06-03 17:00 ` Junio C Hamano
2005-06-03 17:50 ` Linus Torvalds
2005-06-03 17:24 ` Junio C Hamano
2005-06-03 18:30 ` Junio C Hamano
2005-06-03 21:33 ` Daniel Barkalow
2005-06-03 21:59 ` Linus Torvalds
2005-06-03 22:39 ` Petr Baudis
2005-06-04 0:06 ` Daniel Barkalow
2005-06-05 4:47 ` Junio C Hamano
2005-06-05 5:38 ` Daniel Barkalow
2005-06-05 6:48 ` Junio C Hamano
2005-06-05 16:03 ` Daniel Barkalow
2005-06-05 16:17 ` Linus Torvalds
2005-06-05 6:57 ` [PATCH-CAREFUL/RENAME] rename git-rpush and git-rpull to git-ssh-push and git-ssh-pull Junio C Hamano
2005-06-05 16:06 ` Daniel Barkalow
2005-06-05 21:31 ` Linus Torvalds
2005-06-05 22:41 ` Junio C Hamano
2005-06-05 23:17 ` Linus Torvalds
2005-06-05 16:49 ` [PATCH] git-daemon server Jason McMullan
2005-06-05 18:11 ` 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=1117814982.32257.64.camel@jmcmullan.timesys \
--to=jason.mcmullan@timesys.com \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.org \
/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).