From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-31216-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 9388 invoked by alias); 5 Apr 2013 16:11:15 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 31216
Received: (qmail 27583 invoked from network); 5 Apr 2013 16:11:01 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI,
	SPF_HELO_PASS autolearn=ham version=3.3.2
Received-SPF: none (ns1.primenet.com.au: domain at samsung.com does not designate permitted sender hosts)
X-AuditID: cbfec7f4-b7f4c6d0000018de-c2-515ef791f45b
Date: Fri, 05 Apr 2013 17:10:58 +0100
From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: zsh has migrated cvs -> zsh
Message-id: <20130405171058.3d7a0b3d@pwslap01u.europe.root.pri>
In-reply-to: <20130405155922.GA28139@ruderich.org>
References: <20130403225040.GA45406@redoubt.spodhuis.org>
 <20130404163955.0191e5be@pwslap01u.europe.root.pri>
 <20130405094534.04bc1b79@pwslap01u.europe.root.pri>
 <20130405142144.GA17552@ruderich.org>
 <20130405154508.5fe53088@pwslap01u.europe.root.pri>
 <20130405155922.GA28139@ruderich.org>
Organization: Samsung Cambridge Solution Centre
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu)
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
X-Brightmail-Tracker:
 H4sIAAAAAAAAA+NgFuplluLIzCtJLcpLzFFi42I5/e/4Nd2J3+MCDXZstrE42PyQyYHRY9XB
	D0wBjFFcNimpOZllqUX6dglcGcfmHWIvmMFccXLXW5YGxqNMXYycHBICJhKXzr5nhLDFJC7c
	W8/WxcjFISSwlFHi4ac5TBDOciaJvtX32bsYOThYBFQltj3QBmlgEzCUmLppNliziIC4xNm1
	51lAbGEBDYnNDR9ZQWxeAXuJhln9YDangJHEqQcTmSFmrmaSOPzzMxtIgl9AX+Lq309QF9lL
	zLxyhhGiWVDix+R7YEOZBbQkNm9rYoWw5SU2r3nLPIFRYBaSsllIymYhKVvAyLyKUTS1NLmg
	OCk911CvODG3uDQvXS85P3cTIyQIv+xgXHzM6hCjAAejEg+v5e24QCHWxLLiytxDjBIczEoi
	vLLPgUK8KYmVValF+fFFpTmpxYcYmTg4pRoYlTlXLG8U+P2i/BafjGmXtn3SyVr/i+9nB3wz
	bIxr+trKmWKwdulf86id9w6tevQsqfPAhpDaxJX1Bz3vCgtYHRZJc9zHtCRH9MKud8c/yStU
	5cuXPFj1pMPJ6mTBao1LsYtmnf2+cEO3ZNCJptiui9p/2LZq7jD1PXJ+9pmDx6w3ra78Yh+t
	ocRSnJFoqMVcVJwIAD/TpykgAgAA

On Fri, 05 Apr 2013 17:59:22 +0200
Simon Ruderich <simon@ruderich.org> wrote:
> No, AFAIK the website stills needs to be rsynced manually after
> committing the changes in Git. I'm not sure if there's a way to
> automate it (hooks maybe).

Sounds like that probably ought to be a straightforward job for someone
who knows git, assuming we've got a checkout on the server that can be
rsync'd.

pws