Hi all -

I've got a lot of fossil repositories, and for backup purposes I encrypt
and upload them to "cloud storage".

The backup process runs every night, but I don't want to upload repos
which haven't changed.  My initial thought was that I could just do an
sha1 hash of the repo.  But it turns out that just doing the "fossil
upd" to refresh the repo changes its sha1 hash.  Not helpful.

So I tried to find a way to discern whether or not a repo was *really*
different, and I hit upon the following.  I think it would be nice if
there were an easier way.

Here is my "fossilid" script, which gives a single sha1 hash for the
repo.  Note that it checks both the "config" as well as the "timeline"
for changes:


    if [ ! -f "$1" ]
    then
        echo "fossilid needs the name of the repository to 'id'"
        exit 1
    fi

    configsha=`fossil config export all -R $1 - | grep -v '^#'`
    logsha=`fossil timeline -n 10 -R $1`

    echo "$configsha $logsha"| fossil sha - | cut -d' ' -f1




-- 
Please use my GnuPG key "AD29415D" to communicate with me securely


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to