GIT

source: jwiegley.github.io/git-from-the-bottom-up/

 1.Definition of terms

    1. Repository
      • it is a collection of commits
      • it defines HEAD
      • it contains a set of branches and tags
    2. Index
      • changes are first registered in the index
      • it is a way of confirming changes before doing a commit
      • it is also called the staging area
    3. working trees
      • it is any directory on your filesystem which has a repository associated with it
      • typically indicated by the presence of a sub-directory within-it, named: git
      • it includes all the files and subdirectories in that directory
    4. Commit
      • it is a snapshot of your working tree at some point of time
      • it is an archive of what the project`s tree looked like at a past date
      • Whether on your machine or someone else`s 
      • the state of HEAD at the tim your commit is made becomes that commit`s parent
      • this is what creates the notion of a `revision history`
    5. branch
      • it is just a name for a commit
      • it is also called a reference
      • it is a parentage of a commit, which defines its history, and thus the typical notopn of a "branch of development"
    6. tag
      • It is also a name for a commit
      • it is similar to a branch
      • it always names the same commit (<> branch)
      • it can have its own description text
    7. master
      • it is a branch that is called master
      • the mainline of development in most repositoriesis done in master
      • This is a typical default, but it is not special
    8. head
      • it is used by your repository to define what is currently checked out
        • you checkout a branch
          • HEAD symbolically refers to that branch
          • indicating that the branch name should be updated after the next commit operation
        • you checkout a specific commit
          • HEAD refers to that commit only
          • this is referred to as a detached HEAD
          • it occurs if you checkout a tag name

2.workflows

    • you create a repository
      • git checkout
    • you complete your work in the working tree
    • you complete the bugs
    • you are ready to compile
      • git-add
    • you add your changes to the index
    • your changes and all the other are what you intend to commit
      • git commit
    • you record the content of the index in the repository
REPOSITORY ->git-checkout->WORKING TREE->git-add->INDEX->git-commit->REPOSITORY

3. Repository

File system:
  • Root Directory
    • directory A (tree)
      • file A: leaf node A (blob)
        • data1
        • data2
      • file B:leaf node B
      • file C
    • dir B
    • dir C
    • dir D
    • ....

4.Blob

    1. Create repository
    2. Which hash id GIT stores my greetings
      • everybodu even in diff computer will get the same hash id
      • because GIT realize we track the same content
    3. initialize a new repository and commit the file into it
    4. Our blob should be in the sys with the hash id as above
      • usually six digits: af5626
      • or seven af5626k

5.Conclusion

The whole sys is about blob management
Location: Ankara, Türkiye

Comments

Post a Comment

Popular posts from this blog

PHP MYSQL notes

PHP Beginner PHP Array Loop Function Pre-Def variable Session Read Write File CRUD Advanced PHP PHP MySQL PHP MyAdmin PHP MySQL Notes Other course Python Beginner Intermediate Advanced Pro python-hosting React Links General JS PHP Programming Python C++ Stuff TR: Create DB Collation Supported language: gözönünde bulundur Most common: UTF-general-cı Türkçe: ISO 8859-9 (latin5) windows 1254 utf-8 çok daha iyi ama dezavantaj daha çok byte Data Type Int - collation boş - size boş String - bu field her zaman  Char olmalı-çünkü =255 kar
Read more

Programming- AI, machine learning

< JS C C++ Python >< coding Robotics CNC > < Robotics CNC Links > < CNC >< CNC tutorial > < 3d printing >< Azure MongoDB Spark > < AI Pytorch > < Ship building > < GIT >      Data science R For statistical computing Stat modeling data analysis clustering time series forecasting OOP Python, it has a graph and stat packagees Matpotlib Numpy ScipPy Deep Learning packages TensorFlow PyTorch Keras SQL relational db NoSQL; non relational, distributed db MongoDB, Radis, Cassandra Hadoop: Big data; management and storage of huge data It is a storage of Big Data Open source software It uses distributed storage system called Map Reduce PAckages in Hadoop: Pig, Hive, HBase Tableau Data visualization software Specialized in graphical analysis if data Interactive visualisation and dashboards: treemaps, histograms, Box Plots It connects with spreadsheets, DB and cloud Weko For getting familiar with ML in action Open source it was GUI (no co
Read more

Programming -- JS, C, C++, Python

Image
 < JS C C++ Python >< coding Robotics CNC > < Robotics CNC Links > < CNC >< CNC tutorial > < 3d printing >< Azure MongoDB Spark > < AI Pytorch > < Ship building > < GIT >   programming language history  This is taken from somewhere that I have not taken a note. It is a real good work. It describes the root for the languages. I have found this schema on the internet around 2000. And at this time visual basic did not evolved to something new. but got mixed with C# and all other possible language forming .NET which was really good (under c# this is written).  Second note for this schema, although internet was there (since 70`s?) the sofware related to internet did not really show up, and were not really strong enough in the market. The revolutionising of the internet ability changed this schema radically. While there was few programming language at the 90`s, on 2010 there were I guess more than 100 in the market which were active
Read more