All of lore.kernel.org
 help / color / mirror / Atom feed
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 13:18:57 -0400
Date: Fri, 3 Jun 2005 13:12:06 -0400	[thread overview]
Message-ID: <1117819137.32257.75.camel@jmcmullan.timesys> (raw)
In-Reply-To: <Pine.LNX.4.58.0506030929150.1876@ppc970.osdl.org>

[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]

On Fri, 2005-06-03 at 09:30 -0700, Linus Torvalds wrote:
> Well, it's fine, but you should at least tell _how_ you use it. What are
> the scripts you use to synchronize etc etc..

Sorry, here's some use cases (assuming that git-server is running on
192.168.1.1 port 7777)

###### Create a new local git repo

$ GITCONN="--tcp --host 192.168.1.1 --port 7777"
$ git-init-db
$ git-server $GITCONN -- request master



###### Update local repo to remote's head linux-devel

$ git-server $GITCONN -- request linux-devel


###### Create remote head linux-mumble

$ git-server $GITCONN -- head -- linux-mumble
6678abc8d819abc919a018ca89273091bc98a


###### Get remote head's linux-mumble SHA1

$ git-server $GITCONN -- head linux-mumble
sha1 linux-mumble 6678abc8d819abc919a018ca89273091bc98a


###### Set remote head to new SHA1

$ git-server $GITCONN -- head linux-mumble
6678abc8d819abc919a018ca89273091bc98a
8389324a9890218bcd9a0193781abc8a183a9
sha1 linux-mumble 8389324a9890218bcd9a0193781abc8a183a9

(This has the side effect of the server requesting SHA1 objects from the
client if they do not exist on the remote repository)


-- 
Jason McMullan <jason.mcmullan@timesys.com>
TimeSys Corporation


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-06-03 17:15 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
2005-06-03 16:30     ` Linus Torvalds
2005-06-03 17:18       ` McMullan, Jason [this message]
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=1117819137.32257.75.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.