On 13.08.2016 20:21, David Chapman wrote:
> On 8/13/2016 11:07 AM, Adam Jensen wrote:
>> On 08/12/2016 08:56 PM, Adam Jensen wrote:
>>> Here's the situation: I have ~1500 mp3 files (not pirated music), and
>>> the collection is growing. The sizes range from ~100kB to ~300MB. The
>>> content of these files will never change. The directory structure will
>>> change, files will be moved, and new (additional) [mp3] files will
>>> be added.
>> When a branch is created, are the files under revision control in the
>> trunk copied to the branch (is there any duplication of files in the
> No, the files are not copied; a rename is stored. These are "cheap
> copies", and this is an advantage over simple backups - if you want to
> save history using backups (per another suggestion), you need to
> retain one backup per significant event. That can add up.
> Subversion is most often used to store text files because it stores
> intra-file deltas when content is modified. Your use case is unusual,
> but as long as you don't make a lot of changes to the binary files, it
> will be efficient.
Subversion uses binary deltas to store differences between files. It's
essentially irrelevant if the files are text or something else, *unless*
they're compressed (or encrypted) -- deltas between compressed versions
of files with even minor differences are usually quite large, so in such
cases Subversion may end up storing the complete file contents. (MP3
files are compressed audio, which is why I bring this up.)
In any case, Subversion handles binary files just fine. The tree
reorganizations you mention will cause minimal storage overhead.
Received on 2016-08-14 03:28:19 CEST