On Fri, Mar 15, 2013 at 6:18 PM, Christopher Morrow <morrowc.lists@xxxxxxxxx> wrote: > On Fri, Mar 15, 2013 at 12:45 PM, Francis Galiegue <fgaliegue@xxxxxxxxx> wrote: >> On Fri, Mar 15, 2013 at 4:09 PM, Christopher Morrow >> <morrowc.lists@xxxxxxxxx> wrote: >> [...] >> >>> >>> curious why rsync doesn't also seem 'straightforward' and 'well supported' ? >>> >> >> * rsync doesn't prevent corruption of data, git does; > > rsync does do checksums... and are there really that many failures > transfering 10k txt files? > What I mean is that if there is disk corruption on the server hosting the drafts (which can happen post write), rsync will happily send the checksum of the corrupted draft. Git's mechanism makes such a probability infinitesimal. >> * git show, git log, git bisect; >> * git format-patch, git send-email etc. >> >> I second this proposal. > > I wasn't against it, just curious ... since rsync seems to do most of > this (hook it to mail you changes each run...) > It depends on what features you really want out of a "draft revision control system", I suppose ;) -- Francis Galiegue, fgaliegue@xxxxxxxxx JSON Schema in Java: http://json-schema-validator.herokuapp.com