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 [off-list ref]
TimeSys Corporation