Git bundle was designed as a secondary method to the patch refs.
Scenario you want to pass over to a colleague a set of commits before pushing them to remote "git push origin master ...", so you can do one of two things:
by hagzag
tags:
border:
I found this information very supporting during my personal jorney into learning git, the internals IMO shows the mind shift one has to do when using Git after using any other SCM tool.
by hagzag
tags:
border:
~4 years ago I wrote a script which will sync my drupal files directory between two servers [ I used rsync for that ], the problem with rsync was that it fetches a checsum of every file and direcroty over SSH which was very slow, and the critical issue was I have no history of the data - and if I am maintaining multipule syncs whats the point in rsync.
I looked @ svn at the time which was extreemly slow with binaries [ zip, tars etc ], Git and the git protocol in specific did the full sync [ ~1GB ] in under 45 minuets - over the Internet which was quite good IMO.
by gil
tags:
border:
While working with GIT I have encountered something I haven't dealt with in SVN.
I had a very big working copy with very big files (up to 1 GB of size). The total size of the working copy was 10 GB.
After long time investigating and trial and error, I have found out that GIT cannot handle big chunks of data to be pushed so I have tried to add/commit/push only half of the data and then only quarter and so on. Till I got to a point that I have tried to push one file with the size of 800 MB and couldn't.
by yorammi
tags:
border:
Description of a common migration path - SVN to GIT to GitHub.
Preview
This article describes a common migration path - SVN to GIT to GitHub - that I've walked-in lately and can be used as a best-practice for many users even if not used as-is since each case have a different startup-status and different requirements.
The post can be useful for many of you since it contains the following content:
by dmitri
tags:
border:
We are working on a feature branch that we need to keep alive until QA team will be able to test it and create the automatic tests.
For this reason we need to rebase to main dev branch continuously, but each rebase is really hard because we need to resolve many conflicts, and most of the times we need to resolve conflicts already solved in the previous iteration, because the main dev branch contains merge commit that brings in same commits more than once.
How can we avoid that?
by miron
tags:
border:
Moving a +-150 developers dev group from SVN to git is a challenging task. Management wanted some POC and pilot. Team leaders wanted that the team agenda and timeline will be taken under consideration. And no one wanted to decrease productivity more than necessary.
by ittayd
tags:
border:
Git immersion looks like a nice hands-on guide to Git. Short excercises that the student invokes to learn git.
by ittayd
tags:
border:
From the site:
Gitblit is an open-source, pure Java stack for managing, viewing, and serving Git repositories.
It's designed primarily as a tool for small workgroups who want to host centralized repositories.
by igorz
tags:
border:
This tutorial indeed for people who is not familiar with Git and GitHub and make first steps with this this technology. The tutorial contains following steps:
- Installing Git and Git Extensions
- Setting up GitHub account ,SSH keys and repository
- Working with GitHub repository with Git Extensions
- Cloning public repository from GitHub