GIT
  • What is a Version Control System ?
    • How Software would have been developed before '70s?
    • Expectations of a tool
    • Generation of Version Control System
    • The BitKeeper-Git-Mercurial Saga : How a License Agreement Change Shaped the Open-Source World
    • Mercurial was invented by andrew, then why Linus needs to create GIT
  • Git Installation and Initial Configs
  • Basic Terminologies
  • Q1 - Initialize a Repository and Basic Configurations
  • Q2 - Adding and Staging Files
  • Ways to Exclude Files in GIT ?
Powered by GitBook
On this page
  1. What is a Version Control System ?

Expectations of a tool

PreviousHow Software would have been developed before '70s?NextGeneration of Version Control System

Last updated 1 year ago

Now we have some expectations about the tool that we wanted. Let's pen it down.

  1. It should enable multiple people to simultaneously work on a single project.

  1. Each person edits his or her own copy of the files and chooses when to share those changes with the rest of the team. Thus, temporary or partial edits by one person do not interfere with another person's work.

  1. Enables one person to use multiple computers to work on a project, so it is valuable even if you are working by yourself.

  1. 🔥Integration work should be done simultaneously by different team members. In most cases, edits to different files or even the same file can be combined without losing any work.

  1. Historical versions of your project. If you make a mistake, you can roll back to a previous version. You can reproduce and understand a bug report on a past version of your software.