Daniel Jomphe's Library tagged git → View Popular

Filter:
All
Annotated

12 Sep 09

Kirth's Mess » Blog Archive » Starting with Git

blog.kirth.be/...starting-with-git - Preview

git learning

24 Apr 09

DVCSAnalysis - support - Analysis of Git and Mercurial - Google Code

code.google.com/...DVCSAnalysis - Preview

git mercurial comparison

Based on popularity, two distributed version control systems were considered: Git and Mercurial.
One key feature of any DVCS system is to make it easy for repositories to unambiguously describe the history they have (and the history they are requesting). Both Git and Mercurial do this by using SHA1 hashes to identify data (files, trees, changesets, etc).
16 more annotations...
- With Mercurial, if a branch is in the local repository, then all of its revisions (back to the very initial commit) must also be present, and there is no way to prune branches other than by creating a new repository and selectively pulling branches into it.
- Git supports an unlimited number of parent revisions during a merge. Mercurial only allows two parents. In order to achieve an N-way merge in Mercurial, the user will have to perform N-1 two-way merges. Although in many cases this is also the preferred way to merge N parents regardless of DVCS, with Git the user can perform an N-way merge in one step if so desired.
- Mercurial has added rebase support since this analysis was conducted.
- Git has a steeper learning curve than Mercurial due to a number of factors. Git has more commands and options, the volume of which can be intimidating to new users. Mercurial's documentation tends to be more complete and easier for novices to read. Mercurial's terminology and commands are also a closer to Subversion and CVS, making it familiar to people migrating from those systems.
- Git requires periodic maintenance of repositories (i.e. git-gc), Mercurial does not require such maintenance. Note, however, that Mercurial is also a lot less sophisticated with respect to managing the clients disk space
- History is Sacred. Git is extremely powerful, and will do almost anything you ask it to. Unfortunately, this also means that Git is perfectly happy to lose history. For example, git-push --force can result in revisions becoming lost in the remote repository. Mercurial's repository is structured more as an ever-growing collection of immutable objects.
- Git does not explicitly track file renaming or copying. Instead, commands such as git-log look for cases where an identical file appears earlier in the repository history and infers the rename or copy. Mercurial takes the more familiar approach of providing explicit rename and copy commands and storing this as part of the history of a file. Each approach has both advantages and disadvantages, and it isn't clear that either approach is universally "better" than the other.
- Git was originally a large number of shell scripts and unix commands implemented in C. Over time, a common library that shared between commands has been developed, and many of the commands have been built into the main git executable.
- In Git, the default mode of operation is for developers to have their own local (and private) tags/branches/revisions, and exercise a lot of control over what becomes public. With Mercurial the emphasis is the other way around - default push/pull behavior shares all information and extra steps need to be taken to share a subset.
- In Git, each repository has its own branch namespace, and users set up a mapping between local branchnames and remote ones. With Mercurial, there is a single branch namespace shared by all repositories.
- Both Git and Mercurial internally work with very similar data: revisions of files along with a small amount of meta information (parents, author, etc). They both have objects that represent a project-wide commit, and these are also versioned. They both have objects that associate a commit with a set of file versions. In Git, this is a tree object (a tree structure with tree objects for directories and references to file revisions as the leaves). In Mercurial, there is a manifest (a flat list mapping pathnames to file revision objects). Aside from the manifest/tree difference, both are very similar in terms of how objects are searched and walked.
- Mercurial has very good support for HTTP based stateless pushing and pulling of remote repositories.
- Git includes support for HTTP pulls (and WebDAV pushes), but the implementation assumes that the server knows nothing about Git. It is designed such that you can have a Apache simply serve the Git repository as static content. This method requires numerous synchronous round trip requests, and is unsuitable for use in Google Code
- Git also has a custom stateful protocol that supports much faster exchanges of information, but this is not a good match for Google infrastructure. Specifically, it is very desirable to use a stateless HTTP protocol since there is already significant infrastructure in place to make such transactions reliable and performant.
- Git is more powerful, but this tends to be offset by it being more complicated to use.
- As a benchmark, Git and Mercurial repositories were seeded with approximately 1500 files totaling 35 M of data. The servers were running in Chicago and the clients in Mountain View (51 ms ping time). The operation of cloning the remote repository (similar to a initial checkout in traditional version control systems) averaged 8.1 seconds for Mercurial and 178 seconds for Git (22 times slower). A single file in the repository was then changed 50 times and the clients pulled the updates. In this case, Mercurial took 1.5 seconds and Git required 18 seconds (12 times slower). When the Git protocol was used instead of HTTP, Git's performance was similar to Mercurial (8.7 seconds for cloning, 2.8 seconds for the pull).

17 Apr 09

PEP 374 -- Migrating from svn to a distributed VCS

www.python.org/pep-0374 - Preview

vcs dvcs comparison git subversion bazaar mercurial learning

20 Jan 09

My Git Workflow

gweezlebur.com/...my-git-workflow.html - Preview

git learning

16 Jan 09

An Illustrated Guide to Git on Windows

nathanj.github.com/gitguide - Preview

vcs git learning comparison mercurial bazaar subversion

06 Jan 09

Gnome DVCS Survey — GitHub

github.com/...287-gnome-dvcs-survey - Preview

vcs dvcs comparison git bazaar mercurial

08 Dec 08

Insider Guide to GitHub Series — GitHub

github.com/...insider-guide-to-github-series - Preview

learning git github screencastvideo

02 Dec 08

23 Nov 08

git rebase: keeping your branches current :: James Bowes

jbowes.dangerouslyinc.com/...-keeping-your-branches-current - Preview

git learning rebase

20 Nov 08

Documentation of git

grml.org/git - Preview

git learning reference

From subversion to git (part2 - gitweb) » Torsten Curdt’s weblog

vafer.org/20080115011407 - Preview

git learning

Howto/GitPublicRepositoryInstallAndConfigure – TJworld – Trac

tjworld.net/...cRepositoryInstallAndConfigure - Preview

git learning

scie.nti.st » Hosting Git repositories, The Easy (and Secure) Way

scie.nti.st/...tories-the-easy-and-secure-way - Preview

git learning

Deploying a Git Repository Server in Ubuntu « Battery Powered

batterypowered.wordpress.com/...it-repository-server-in-ubuntu - Preview

git learning

19 Nov 08

codeslower.com

blog.codeslower.com/...ss-GitHub-repositories-via-SSH - Preview

git proxy https

03 Nov 08

Git changes how developers manage source code versions - SD Times On The Web

www.sdtimes.com/33018 - Preview

vcs comparison dvcs git subversion

It decouples the notion of checkpointing from publishing. In Subversion, those are the same thing
Git lets developers experiment with the whole of a project, without worrying about breaking things or losing work
2 more annotations...
- With Git running locally, developers push commits whenever they feel like and can fork and experiment to their hearts’ content. Those changes won't bother anyone “until you share [them],” said Vilain. “You share at the end of the day, after a day's work, when you've gone over the code a bit more.”
- “The reason that most of us use it is that it helps productivity,” said Scott Chacon, a developer at GitHub. “It provides cheap local branching. It works for really big repositories and really small repositories. And it’s free, and it’s easy to get.

25 Oct 08

linux.dell.com Git

linux.dell.com/git - Preview

git user dell

Git Resources

37s.backpackit.com/1465067 - Preview

git learning

1 - 20 of 114 Next › Last »

Showing 20▼ items per page

Selected Tags

Related Tags

Top Contributors

Click in to find related links.

Groups interested in git

git-vs-mercurial-vs-bazaar

Members (2)

bookmarks (35)
dvcs-vs-vcs

Members (2)

bookmarks (30)
learning-git

Members (2)

bookmarks (61)

Related Lists on Diigo

git

Items: 11 | Visits: 28

Created by: Wang Bin
Git

Items: 9 | Visits: 60

Created by: lei zhou
Version Control Info

Pages and howtos about vers...

Items: 1 | Visits: 31

Created by: John Cooper

Diigo is about better ways to research, share and collaborate on information. Learn more »

Join Diigo

Daniel Jomphe's Library tagged git → View Popular

Kirth's Mess » Blog Archive » Starting with Git

DVCSAnalysis - support - Analysis of Git and Mercurial - Google Code

PEP 374 -- Migrating from svn to a distributed VCS

My Git Workflow

An Illustrated Guide to Git on Windows

Gnome DVCS Survey — GitHub

Insider Guide to GitHub Series — GitHub

Andy Delcambre: Git SVN Workflow

$ cheat git

Why Git is Better Than X

git rebase: keeping your branches current :: James Bowes

Documentation of git

From subversion to git (part2 - gitweb) » Torsten Curdt’s weblog

Howto/GitPublicRepositoryInstallAndConfigure – TJworld – Trac

scie.nti.st » Hosting Git repositories, The Easy (and Secure) Way

Deploying a Git Repository Server in Ubuntu « Battery Powered

codeslower.com

Git changes how developers manage source code versions - SD Times On The Web

linux.dell.com Git

Git Resources

Selected Tags

Related Tags

Sponsored Links

Top Contributors

Groups interested in git

git-vs-mercurial-vs-bazaar

dvcs-vs-vcs

learning-git

git

Git

Version Control Info