Control of versions for large files



  • migrating from SVN to GIT.

    In SVN, there was a big tree, which was rarely pumped in the whole - it was decided by many small repositories in git.

    But there's only one problem - big files that require control of versions (graphic, binary).

    1. git is bad.
    2. clone such repository will be made For a few hours, and who needs it in that arm.
    3. All used to cake.

    Advise a version control system for them combining SVN capabilities

    • store only changes
    • only last audit and working catalogue
    • user-friendly interface
    • the possibility of working from the command line

    and git

    • Quick and normal work with the injection
    • the possibility of working without direct access to the repository or having several mirrors of central repository.


  • In fact, you don't have a lot of options, either. https://www.mercurial-scm.org/ which is not too good to store binary files, for example, but gives a good story of winds and https://habrahabr.ru/post/168675/ Either you use GIT.
    And for a user-friendly interface, use the client to control the versions, for example, https://www.sourcetreeapp.com/ or GitHub, if you decide to stay on Git.


    And in fact, about the choice between Git and Mercurial, it's already gone. https://stackoverflow.com/questions/35837/what-is-the-difference-between-mercurial-and-git ♪




Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2