On Wed, Feb 8, 2017 at 8:22 AM, Pavol Lisy <pavol.l...@gmail.com> wrote:
>>> How about graphic and video designers? Just how well does hg cope with
>>> gigabytes of video data?
>>
>> I've no idea, but I know that git can handle large amounts of data.
>> (There are a couple of extensions that make it easier.)
>
> But there could be problem with "keeping eye" part of your premise.
> ("If you commit everything to git and keep an eye on your diffs before
> you push, the encryption would have to be _extremely_ sneaky").True, which is why as much as possible should be done with raw video data that never changes, and then text files that indicate the alterations. The raw video data gets recorded once and then kept as-is, and then your editing work gets saved into some textual form (maybe a JSON file, maybe a series of commands) that you can plausibly diff. The only time you actually add binary files is when you do initial recording work, and a diff that affects those files should always be suspicious. (Obviously it would be horrendously inefficient to work from the raw files all the time. But the edited files could be gitignored, since they can be reconstructed from the originals; share them for convenience, but don't sweat their loss.) ChrisA -- https://mail.python.org/mailman/listinfo/python-list
