![]() Consider tuning up your `~/.gitconfig` (later) **git** has a powerful and very flexible configuration system. **why?** because **git** and **git-annex** are great and we have lots ofĭata already - we needed a _unified distribution_ to index and access it all Manipulate (obtain, create, update, publish, etc.) datasets and **why?** because **git** is great to version text but sucks for dataĭataLad provides a unified data distribution with the convenience It aims to solve the problem of sharing and synchronizingĬollections of large files independent from a commercial service or Git-annex is a distributed file synchronization system written in Git-annex allows managing files with git, without checking the file **why?** because **git** is great, but there were no public hosting Tracking, feature requests, task management, and wikis for It offers accessĬontrol and several collaboration features such as bug GitHub is a web-based Git or version control repository and **why?** because Linus needed a FOSS VCS to develop Linux kernel Unusually rich command set that provides both high-level operations and Git is a fast, scalable, distributed revision control system with an from future "repeatable-research" (still applies) because it makes it easy to collaborate Why to use version control systems (VCS)? How to obtain, manage, and share code and data using VCS ![]() How git-annex and DataLad build atop git Warm-up with a typical git/github workflow ![]() # Using version control for code and data ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |