Timeline for Best way to perform version control on Unity projects
Current License: CC BY-SA 4.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 20, 2020 at 9:12 | history | edited | CommunityBot |
Commonmark migration
|
|
May 13, 2019 at 14:13 | history | edited | Fattie | CC BY-SA 4.0 |
added 296 characters in body
|
May 25, 2018 at 17:05 | history | edited | Fattie | CC BY-SA 4.0 |
deleted 529 characters in body
|
May 22, 2016 at 11:11 | vote | accept | gabicuesta | ||
May 2, 2016 at 13:01 | comment | added | Fattie | indeed. you sometimes get "git v. svn" wars (which I could not care less about). it's jus that in the Unity "industry" it's usually subversion. If you engineer Unity for a living most large clients will be svn. | |
May 2, 2016 at 11:46 | comment | added | tgharold | I agree strongly that for large (over 5MB) binary files, Subversion is a far better solution then git. For one thing, you can choose to only bring down part of a repository (sparse working copy), which means if the repository is 10-15GB, you don't have to bring it all down (just the folder that you care about). It also stores deltas instead of full snapshots, plus is efficient across the wire for binary files. The downside is that you must adopt the mantra of "update, modify, commit" in short cycles to avoid conflicts. | |
Apr 30, 2016 at 13:06 | history | edited | Fattie | CC BY-SA 3.0 |
deleted 2 characters in body
|
Apr 30, 2016 at 12:59 | history | edited | Fattie | CC BY-SA 3.0 |
added 227 characters in body
|
Apr 30, 2016 at 12:54 | history | edited | Fattie | CC BY-SA 3.0 |
added 227 characters in body
|
Apr 30, 2016 at 12:48 | history | answered | Fattie | CC BY-SA 3.0 |