My understanding of Git
•Download as KEY, PDF•
0 likes•790 views
This document provides an overview of git and compares it to SVN (Subversion). It notes that git was initially created by Linus Torvalds for Linux kernel development. It highlights key differences between git and SVN such as git being distributed while SVN is centralized, and git tracking the repository while SVN tracks files/folders. The document emphasizes that understanding git requires unlearning how SVN works. It provides some links to additional resources on git.
Report
Share
Report
Share
Recommended
Introduction into GIT
Git is a version control system initially created by Linus Torvalds for Linux kernel development. It is a distributed system, meaning the full history of the codebase is hosted on each user's machine rather than a centralized server. This makes it more robust than centralized systems like SVN - even if the remote server is unavailable, users can still work on code independently and sync up later. Git is also generally faster than SVN, with smaller file sizes and quicker upload/download times for projects of the same size due to its distributed nature.
Dcvs
The document discusses different version control systems (VCS) such as Bazaar, Mercurial, and GIT. GIT is described as being cross-platform using C, with hosting on sites like GitHub and Gitorious. GIT originated in April 2005 with 1244 lines of code and was designed by Linus Torvalds as a replacement for Bitkeeper. Key GIT features highlighted include rebasing, bisecting, and its robust and easy-to-use functionality for managing single patches and code history.
Introduction to Git and GitHub #git_nyan
This document provides an introduction to Git and GitHub. It discusses the history and advantages of Git, including how it was created by Linus Torvalds to support the development of Linux. Key features of Git like reliability, speed, distributed nature, and content management are highlighted. GitHub is introduced as a hosting site for Git repositories. Best practices for Git like separate commits, good commit messages, and GitHub flow are covered. Open source licensing and community aspects are also discussed.
LAB - How to Git
We'll cover the basics of how to use Git , the basics of distributed versioning in Perforce , and gain an understanding of the tradeoffs between the two
Helios in Action: Git at Eclipse
The document discusses Git and Eclipse tools for working with Git. It describes EGit, an Eclipse plugin that provides integration with Git repositories, and JGit, a Java library for Git. EGit and JGit are open source projects hosted by the Eclipse Foundation. The document outlines features and history of EGit releases and the goal of building a community around Git usage at Eclipse.
我对ORM的思考
This document discusses the benefits of using an object-relational mapping (ORM) framework. It explains that ORMs allow developers to work with objects in code while the ORM handles the conversion between objects and relational data in the database. This avoids the need to write manual SQL queries and allows developers to focus on business logic rather than data access code. The document also provides examples of how ORMs can efficiently execute queries and fetch records from the database.
Migrate PHP E-Commerce Site to Go
This document summarizes one company's experience migrating their PHP e-commerce site to the Go programming language. It discusses how they initially rewrote their catalog page in AngularJS and Go, but ran into issues with Facebook OpenGraph integration. For their second release, they decided on a hybrid PHP and Go approach, with Go used to power specific backend modules like caching and shopping cart functionality. The author reflects on lessons learned around thoroughly evaluating new technologies before deploying them and making sure any changes have team consensus.
Recommended
Introduction into GIT
Git is a version control system initially created by Linus Torvalds for Linux kernel development. It is a distributed system, meaning the full history of the codebase is hosted on each user's machine rather than a centralized server. This makes it more robust than centralized systems like SVN - even if the remote server is unavailable, users can still work on code independently and sync up later. Git is also generally faster than SVN, with smaller file sizes and quicker upload/download times for projects of the same size due to its distributed nature.
Dcvs
The document discusses different version control systems (VCS) such as Bazaar, Mercurial, and GIT. GIT is described as being cross-platform using C, with hosting on sites like GitHub and Gitorious. GIT originated in April 2005 with 1244 lines of code and was designed by Linus Torvalds as a replacement for Bitkeeper. Key GIT features highlighted include rebasing, bisecting, and its robust and easy-to-use functionality for managing single patches and code history.
Introduction to Git and GitHub #git_nyan
This document provides an introduction to Git and GitHub. It discusses the history and advantages of Git, including how it was created by Linus Torvalds to support the development of Linux. Key features of Git like reliability, speed, distributed nature, and content management are highlighted. GitHub is introduced as a hosting site for Git repositories. Best practices for Git like separate commits, good commit messages, and GitHub flow are covered. Open source licensing and community aspects are also discussed.
LAB - How to Git
We'll cover the basics of how to use Git , the basics of distributed versioning in Perforce , and gain an understanding of the tradeoffs between the two
Helios in Action: Git at Eclipse
The document discusses Git and Eclipse tools for working with Git. It describes EGit, an Eclipse plugin that provides integration with Git repositories, and JGit, a Java library for Git. EGit and JGit are open source projects hosted by the Eclipse Foundation. The document outlines features and history of EGit releases and the goal of building a community around Git usage at Eclipse.
我对ORM的思考
This document discusses the benefits of using an object-relational mapping (ORM) framework. It explains that ORMs allow developers to work with objects in code while the ORM handles the conversion between objects and relational data in the database. This avoids the need to write manual SQL queries and allows developers to focus on business logic rather than data access code. The document also provides examples of how ORMs can efficiently execute queries and fetch records from the database.
Migrate PHP E-Commerce Site to Go
This document summarizes one company's experience migrating their PHP e-commerce site to the Go programming language. It discusses how they initially rewrote their catalog page in AngularJS and Go, but ran into issues with Facebook OpenGraph integration. For their second release, they decided on a hybrid PHP and Go approach, with Go used to power specific backend modules like caching and shopping cart functionality. The author reflects on lessons learned around thoroughly evaluating new technologies before deploying them and making sure any changes have team consensus.
Introduction to Git
If you've seen my "intro to Git" talk on Google Video, this is the slide deck from that, revised slightly.
Introduction to Git
An introduction to the world of Git from a historical and practical prospective. Common operations and setup scenarios are covered.
January 2022: Central Iowa Linux Users Group: Git
This document provides an overview of the history and features of Git version control software. It discusses earlier version control systems like SCCS and CVS, and how Git was created in 2005 by Linus Torvalds with goals of speed, data integrity, and supporting distributed non-linear workflows. The document outlines some key features of Git like distributed versioning and atomic commits, as well as potential downsides like dealing with large binary files. It also briefly introduces Git LFS as an extension for managing large files outside of the main Git repository.
Mozammel Haque: Git -- Stupid, Fast, distributed content tracker
Git is a distributed version control system that provides fast, reliable management of source code and files. It was chosen over other SCMs like SVN at Therap due to git being distributed, allowing multiple repositories, and commits being atomic. Therap experienced faster updates between repositories, safer storage of code history across 30+ repositories, and easy branching with git compared to their previous system TLA, making development more efficient.
Git vs svn
Git allows for a distributed model where every user has their own local copy of the code and changes are merged to a local master branch, while SVN uses a centralized model where changes are committed to a central repository. Git operations like diff and commit are much faster since they are performed locally without network latency. Git also uses much less storage space than SVN. A key advantage of Git is its powerful branching and merging capabilities.
Git for Android Developers
This document summarizes a presentation about using Git for Android development. The presentation introduces basic Git commands like init, add, commit, log and tag. It explains Git concepts such as blobs, trees and commits. The presentation also covers branching, merging, rebasing and tools for collaborating with Git. Attendees are encouraged to learn Git through hands-on use and experimentation.
Git
Git is a widely used distributed version control system that provides several advantages over centralized systems like SVN. It allows for distributed, offline development and easy branching and merging of code. Some key benefits include faster cloning and committing, smaller repository sizes, and easier integration of changes from multiple developers. While it has a steeper learning curve initially, Git usage is growing rapidly as more projects adopt it for version control.
simple Introduction to git
simple introduction to git, show popular commands, git friends and compare with svn in this presentation
Git! Why? How?
The document discusses why developers should use Git over Subversion (SVN) for version control, explaining that Git was created by Linus Torvalds as a distributed system that is optimized for workflows like branching, merging, and handling large codebases. It provides an overview of Git's core features like snapshots instead of differences, distributed model instead of centralized server, and various tools that can be used with Git. The document concludes by recommending that the company Namics switch from using SVN to using Git for version control.
An introduction to Git.
The document discusses Git, an open source distributed version control system originally designed and developed by Linus Torvalds. It provides information on why Git is useful for group work, allowing developers to work offline and easily branch and merge files. The document then demonstrates how Git works with developers committing changes to local repositories and pushing them to a shared central repository. It provides guidance on setting up Git with GitHub and gives an overview of common Git commands.
GIT for version control- A very comprehensive guide .pptx
Git is a version control system created by Linus Torvalds in 2005 to manage changes to code during software development. It allows for non-linear development through parallel branches and is fully distributed, enabling efficient management of large projects. Basic Git commands include git config to set up user information, git add to stage files for commits, and git commit to save file changes to the project history.
An introduction to git
git Workshop slides conducted at Lahore Civic Hackathon organized by CodeForPakistan.org 25, January, 2014 @ LUMS, Lahore.
Introduction to git
This introduction to Git provides a quick head start for someone new to using Git, and thinking of migration from Subversion. This provides basic git details and some strategies I believe are helpful for teams onboarding to git
Intro to Git
Linus Torvalds created Git as a distributed revision control system after needing an alternative to BitKeeper for the Linux kernel project. Git allows independent and distributed control over versions of files without needing a central server. Popular projects like Twitter, Facebook, and CakePHP use Git due to its fast and distributed nature. Source code, documents, images and other files can be stored in Git repositories. Basic Git workflows involve cloning or initializing a repository, making changes, committing changes locally, merging conflicts if any, and pushing changes to a remote repository.
Enterprise git
The document discusses why Git is a useful version control system. It notes that Git is fast, secure, distributed, and cross-platform. It works well for both large and small teams. The document outlines some common branch naming conventions like using "master" for production, "release/*" for releases, and "feature/*" for new features. It recommends starting with best practices and choosing whatever source control works for your team.
Git: be social
This document introduces version control systems and Git. It discusses the history and features of Git, how it differs from centralized and local version control systems in using a distributed and non-linear model. The document then provides a tutorial on basic Git commands and workflows for initializing and cloning repositories, tracking and committing changes, viewing history and undoing changes, working with remote repositories, tagging, and using branches.
Harvard ABCD-WWW Git presentation
This document introduces version control and Git. It explains that Git is a distributed version control system created by Linus Torvalds that is widely used, especially for open source projects. It discusses what source control is and why it is useful, particularly for tracking changes on a line-by-line basis. The document outlines some key Git commands and concepts like branching, merging, and undoing changes. It notes both advantages of Git like its speed and cheap branching, and disadvantages like its complexity and better suitability for code vs binary files. Overall, the document provides a high-level overview of what Git is and why it is useful for software development.
Why Git Sucks and you'll use it anyways
The document discusses the pros and cons of using Git. It acknowledges that Git is complex and unintuitive, but argues people will still use it because distributed version control encourages contributions and experimentation through easy branching. It also notes many popular open source projects use Git. The document then provides a basic overview of how to get started with Git configuration, cloning repositories, committing changes, branching, merging, and interacting with remote repositories on services like GitHub.
sbt 1
This document provides an overview of sbt 1, including:
- Who is developing sbt 1 (Lightbend Tooling team led by Eugene Yokota and Dale Wijnand)
- Key updates in sbt 1 like using Scala 2.12, Zinc incremental compiler, improved library management, and removal of old parts
- Goals of sbt 1 like minimizing conceptual jump from sbt 0.13
- Size of the sbt ecosystem with hundreds of thousands of downloads and over 400 community plugins
- Ways to get involved like helping with documentation, issue triage, or contributing patches
Git Presentation
Presentation deals
Visualizing SVN vs Git
Git architecture
Delta storage
Branching and Rebase
Git commands
About Caching
Caching is used to optimize performance by taking advantage of different access speeds of storage mediums. It stores frequently accessed data in faster storage like memory or disk cache. There are different types of caches like browser cache, server cache using memcached, and cache within a request. Memcached is mainly used for read-through caching but has issues like requiring separate deployment and CAS operations. GroupCache is an alternative that avoids duplicated calls to the backend and has better performance without network IO or CAS. Write-through caching aims to have zero reads from the backend but is challenging to implement transactionally at scale.
Metaprogramming Go
Illustrate different scenarios of using Metaprogramming Go with actual example; using py for quite PoC. Opening talk for PyCon 2014 China.
More Related Content
Similar to My understanding of Git
Introduction to Git
If you've seen my "intro to Git" talk on Google Video, this is the slide deck from that, revised slightly.
Introduction to Git
An introduction to the world of Git from a historical and practical prospective. Common operations and setup scenarios are covered.
January 2022: Central Iowa Linux Users Group: Git
This document provides an overview of the history and features of Git version control software. It discusses earlier version control systems like SCCS and CVS, and how Git was created in 2005 by Linus Torvalds with goals of speed, data integrity, and supporting distributed non-linear workflows. The document outlines some key features of Git like distributed versioning and atomic commits, as well as potential downsides like dealing with large binary files. It also briefly introduces Git LFS as an extension for managing large files outside of the main Git repository.
Mozammel Haque: Git -- Stupid, Fast, distributed content tracker
Git is a distributed version control system that provides fast, reliable management of source code and files. It was chosen over other SCMs like SVN at Therap due to git being distributed, allowing multiple repositories, and commits being atomic. Therap experienced faster updates between repositories, safer storage of code history across 30+ repositories, and easy branching with git compared to their previous system TLA, making development more efficient.
Git vs svn
Git allows for a distributed model where every user has their own local copy of the code and changes are merged to a local master branch, while SVN uses a centralized model where changes are committed to a central repository. Git operations like diff and commit are much faster since they are performed locally without network latency. Git also uses much less storage space than SVN. A key advantage of Git is its powerful branching and merging capabilities.
Git for Android Developers
This document summarizes a presentation about using Git for Android development. The presentation introduces basic Git commands like init, add, commit, log and tag. It explains Git concepts such as blobs, trees and commits. The presentation also covers branching, merging, rebasing and tools for collaborating with Git. Attendees are encouraged to learn Git through hands-on use and experimentation.
Git
Git is a widely used distributed version control system that provides several advantages over centralized systems like SVN. It allows for distributed, offline development and easy branching and merging of code. Some key benefits include faster cloning and committing, smaller repository sizes, and easier integration of changes from multiple developers. While it has a steeper learning curve initially, Git usage is growing rapidly as more projects adopt it for version control.
simple Introduction to git
simple introduction to git, show popular commands, git friends and compare with svn in this presentation
Git! Why? How?
The document discusses why developers should use Git over Subversion (SVN) for version control, explaining that Git was created by Linus Torvalds as a distributed system that is optimized for workflows like branching, merging, and handling large codebases. It provides an overview of Git's core features like snapshots instead of differences, distributed model instead of centralized server, and various tools that can be used with Git. The document concludes by recommending that the company Namics switch from using SVN to using Git for version control.
An introduction to Git.
The document discusses Git, an open source distributed version control system originally designed and developed by Linus Torvalds. It provides information on why Git is useful for group work, allowing developers to work offline and easily branch and merge files. The document then demonstrates how Git works with developers committing changes to local repositories and pushing them to a shared central repository. It provides guidance on setting up Git with GitHub and gives an overview of common Git commands.
GIT for version control- A very comprehensive guide .pptx
Git is a version control system created by Linus Torvalds in 2005 to manage changes to code during software development. It allows for non-linear development through parallel branches and is fully distributed, enabling efficient management of large projects. Basic Git commands include git config to set up user information, git add to stage files for commits, and git commit to save file changes to the project history.
An introduction to git
git Workshop slides conducted at Lahore Civic Hackathon organized by CodeForPakistan.org 25, January, 2014 @ LUMS, Lahore.
Introduction to git
This introduction to Git provides a quick head start for someone new to using Git, and thinking of migration from Subversion. This provides basic git details and some strategies I believe are helpful for teams onboarding to git
Intro to Git
Linus Torvalds created Git as a distributed revision control system after needing an alternative to BitKeeper for the Linux kernel project. Git allows independent and distributed control over versions of files without needing a central server. Popular projects like Twitter, Facebook, and CakePHP use Git due to its fast and distributed nature. Source code, documents, images and other files can be stored in Git repositories. Basic Git workflows involve cloning or initializing a repository, making changes, committing changes locally, merging conflicts if any, and pushing changes to a remote repository.
Enterprise git
The document discusses why Git is a useful version control system. It notes that Git is fast, secure, distributed, and cross-platform. It works well for both large and small teams. The document outlines some common branch naming conventions like using "master" for production, "release/*" for releases, and "feature/*" for new features. It recommends starting with best practices and choosing whatever source control works for your team.
Git: be social
This document introduces version control systems and Git. It discusses the history and features of Git, how it differs from centralized and local version control systems in using a distributed and non-linear model. The document then provides a tutorial on basic Git commands and workflows for initializing and cloning repositories, tracking and committing changes, viewing history and undoing changes, working with remote repositories, tagging, and using branches.
Harvard ABCD-WWW Git presentation
This document introduces version control and Git. It explains that Git is a distributed version control system created by Linus Torvalds that is widely used, especially for open source projects. It discusses what source control is and why it is useful, particularly for tracking changes on a line-by-line basis. The document outlines some key Git commands and concepts like branching, merging, and undoing changes. It notes both advantages of Git like its speed and cheap branching, and disadvantages like its complexity and better suitability for code vs binary files. Overall, the document provides a high-level overview of what Git is and why it is useful for software development.
Why Git Sucks and you'll use it anyways
The document discusses the pros and cons of using Git. It acknowledges that Git is complex and unintuitive, but argues people will still use it because distributed version control encourages contributions and experimentation through easy branching. It also notes many popular open source projects use Git. The document then provides a basic overview of how to get started with Git configuration, cloning repositories, committing changes, branching, merging, and interacting with remote repositories on services like GitHub.
sbt 1
This document provides an overview of sbt 1, including:
- Who is developing sbt 1 (Lightbend Tooling team led by Eugene Yokota and Dale Wijnand)
- Key updates in sbt 1 like using Scala 2.12, Zinc incremental compiler, improved library management, and removal of old parts
- Goals of sbt 1 like minimizing conceptual jump from sbt 0.13
- Size of the sbt ecosystem with hundreds of thousands of downloads and over 400 community plugins
- Ways to get involved like helping with documentation, issue triage, or contributing patches
Git Presentation
Presentation deals
Visualizing SVN vs Git
Git architecture
Delta storage
Branching and Rebase
Git commands
Similar to My understanding of Git (20)
Mozammel Haque: Git -- Stupid, Fast, distributed content tracker
Mozammel Haque: Git -- Stupid, Fast, distributed content tracker
GIT for version control- A very comprehensive guide .pptx
GIT for version control- A very comprehensive guide .pptx
More from Weng Wei
About Caching
Caching is used to optimize performance by taking advantage of different access speeds of storage mediums. It stores frequently accessed data in faster storage like memory or disk cache. There are different types of caches like browser cache, server cache using memcached, and cache within a request. Memcached is mainly used for read-through caching but has issues like requiring separate deployment and CAS operations. GroupCache is an alternative that avoids duplicated calls to the backend and has better performance without network IO or CAS. Write-through caching aims to have zero reads from the backend but is challenging to implement transactionally at scale.
Metaprogramming Go
Illustrate different scenarios of using Metaprogramming Go with actual example; using py for quite PoC. Opening talk for PyCon 2014 China.
Why use Go for web development?
This document discusses the suitability of Go for web development. It notes that while Go's built-in HTML template engine is basic, the Gorazor template engine provides a more powerful way to mix Go code into HTML templates. Code generation approaches also allow Go to behave more dynamically at runtime. Go's fast compilation and use of interfaces make it well-suited for dynamic web applications and large websites. The document concludes that while other languages may be more mature, Go is suitable for developing large, stable, scalable websites that need to be maintained over time.
Go for web
1. Go is a programming language designed by Google to help solve Google's "big problems".
2. Go provides garbage collection, concurrency features, and static typing for building scalable and reliable systems.
3. Go can be used to build web applications and services using the net/http package for HTTP servers and clients.
Python to go
The author explains why they switched from primarily using Python to primarily using Go for serious projects. Some key reasons include that Go has better performance, code quality, testing, and concurrency features compared to Python. While Python is still good for hobby projects, Go enforces error handling, has built-in profiling tools, and makes deployment easier due to compiling to a single binary.
A byte of git
This document discusses the key concepts and advantages of using Git over Subversion (SVN) for version control. It notes that while Git has a steeper learning curve due to its distributed and nonlinear model, it offers benefits like faster and easier branching, merging, and deployment. The document demonstrates several Git commands and techniques through examples, such as staging changes, amending commits, rebasing branches, and using Git for deployment to Heroku. It also addresses access control and GUI options for Git.
Sharding
Sharding is a technique for scaling databases by partitioning data across multiple database servers or nodes. There are different ways to implement sharding such as sharding on the primary key or an index in a relational database. For key-value stores, a common approach is to hash the key and assign it to a node using consistent hashing. While sharding improves scalability, it also introduces some limitations like not being able to perform joins across shards and additional work required for data maintenance.
Inside Zend Framework
The document discusses the inner workings of Zend Framework, including its use of .htaccess and index.php files to bootstrap the application. It describes how Zend/Application/Bootstrap/BootstrapAbstract.php and application-specific bootstrap files are used to initialize the application. The front controller pattern is implemented using Zend/Application/Resource/Frontcontroller.php. Routing is handled by Zend/Controller/Router modules which dispatch requests to controllers and actions. While the framework aims to be simple through convention over configuration, it can also be complex under the hood. Zend Framework 2 refactored some components, such as the database adapter, for improved architecture.
More from Weng Wei (13)
My understanding of Git
- 1. My understanding of git weng.wei@zalora.sg
- 2. Meta • No silver bullets
- 3. Conservation of Complexity • “Complexity has to go somewhere.” - Bjarne Stroustrup • http://www.johndcook.com/blog/ 2009/09/16/conservation-of-complexity/
- 4. Background • Git was initially designed and developed by Linus Torvalds for Linux kernel development
- 5. • Linus Torvalds on git • http://www.youtube.com/watch? v=4XpnKHJAok8
- 6. Linus Torvalds • “Take CVS(Subversion was ‘CVS done right’) as an example of what not to do; if in doubt, make the exact opposite decision. ” • http://en.wikipedia.org/wiki/Git_(software)
- 7. SVN vs Git SVN Git Centralized Distributed Track files / folders Track Repository Revision history is sacred Editing history is common(*) Big Merge/Commit Merge/Commit Early / Fast About revision About changeset
- 8. • In order to learn GIT, one must unlearn SVN.
- 9. Revision vs ChangeSet • Japanese addresses: No street names. Block numbers. • http://sivers.org/jadr
- 14. • http://hginit.com • hg (mercurial) - “easy GIT” with better windows support
- 15. Conservation of Complexity • Easy GIT? • Windows?
- 16. Rebase
- 22. Demo
- 23. • Yes, git looks good, but SVN is also good enough. • We’ve been using SVN for years! We survive and succeed. Why bother?
- 24. • "tinker and fix things that aren't broken" - The greatest geek who ever lived • http://theoatmeal.com/comics/tesla
Editor's Notes
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n