5 ms·

The sheer number of symlinks put me off git-annex.

• icebraining 12y ago
  You should try the direct mode, then: http://git-annex.branchable.com/direct_mode/ http://git-annex.branchable.com/direct_mode/ Normally, git-annex repositories consist of symlinks that are checked into git, and in turn point at the content of large files that is stored in .git/annex/objects/. Direct mode gets rid of the symlinks.
  • nodata 12y ago
    With direct mode, you're operating without large swathes of git-annex's carefully constructed safety net, which ensures that past versions of files are preserved and can be accessed. With direct mode, any file can be edited directly, or deleted at any time, and there's no guarantee that the old version is backed up somewhere else. Yikes!
    • icebraining 12y ago
      If you edit a file in Dropbox without it having had time to sync the previous version, what do you think it'll happen? Git-annex with symlinks can add an extra layer of protection, in that you have to unlock the file before editing, so that it can ensure it has backed up. In direct mode, it just works like any other syncing systems - non-synced versions are lost.
      • maccard 12y ago
        > Git-annex with symlinks can add an extra layer of protection, in that you have to unlock the file before editing Is that like how Perforce handles it?
        • icebraining 12y ago
          I wouldn't know, I never used Perforce. But there's a walkthrough for that: http://git-annex.branchable.com/walkthrough/modifying_annexed_files/ http://git-annex.branchable.com/walkthrough/modifying_annexe... That's without the Assistant, which further simplifies the latter steps by automatically taking care of committing and such. You just do unlock <file>, edit, then add <file>.