分散バージョン管理システムGit入門 - SourceForge.JP Magazine
http://sourceforge.jp/magazine/09/02/02/0655246
git-cheat-sheet-large.png (PNG Image, 3300x2550 pixels)
http://ktown.kde.org/~zrusin/git/git-cheat-sheet-large.png
GitHub Pages — GitHub
http://github.com/blog/272-github-pages

nice. static pages only, but nice.

cf "access control and version control: an overconstrained problem?"

More about the decentralisation of IT

"GitTorrent makes Git truly distributed. The initial plans are for reducing mirror loading, however the full plans include totally distributed development: no central mirrors whatsoever. PGP signing and other web-of-trust-based mechanisms will take over from protocols on ports (e.g. ssh) as the access control "clearing house". The implications of a truly distributed revision control system are truly staggering: unrestricted software freedom

That's exactly what I am looking for - yeah!

Imagine that an entire project - its web site, documentation, wiki, bug-tracker, source code and binaries are all managed and stored in a peer-to-peer distributed git repository.

"GitTorrent makes Git truly distributed. The initial plans are for reducing mirror loading, however the full plans include totally distributed development: no central mirrors whatsoever. PGP signing and other web-of-trust-based mechanisms will take over from protocols on ports (e.g. ssh) as the access control "clearing house". "

From a simple, simple project that is suffering from an inexplicable near complete lack of attention from the free software community comes a revolutionary change in the way that free software is developed and distributed. [[Reminds me of Kragen’s “[What’s wrong with HTTP?](http://lists.canonical.org/pipermail/kragen-tol/2006-November/000841.html)” article. —Ed.]]

GitTorrent makes Git truly distributed. The initial plans are for reducing mirror loading, however the full plans include totally distributed development: no central mirrors whatsoever. PGP signing and other web-of-trust-based mechanisms will take over from protocols on ports (e.g. ssh) as the access control "clearing house".

Lately I’ve been helping a few people to get started on Github. I use git at the command line and my survival guide is also based on that way of interacting with Git. So I thought I’d write the procedure up so that I can just point people to this page.

How to recover your project if git hub goes down.

Thanks! I am going to cancel my github account so this will be useful

git instaweb --httpd=webrick FTW.

GitHub is awesome, really awesome for open source projects and for projects with multiple people. In fact, if you use your own git setup for an open source project, you are most likely hindering your project’s progress and wasting your time. On the other side of the coin, if you are a lone shark and you don’t need GitHub’s awesome social features, I have news for you: you can host your own git repositories really easily and on the cheap side. Remote Setup If you are like me, you probably have a DreamHost, TextDrive or some other cheap shared hosting account with ssh access. What you might not know is that is all you need to host your own private git repositories. ssh username@yourcheaphost.com mkdir -p ~/git/yourproject.git cd ~/git/yourproject.git git --bare init That is it. Your git repository is now setup. Not too hard eh? You could put that anywhere but a folder named git makes sense to me. Local Setup So your remote server is now setup, but how do you use it? Glad you asked.

that was easy

At Hashrocket we use git both internally and in our Agile mentoring and training. Git gives us the flexibility to design a version control workflow that meets the needs of either a fully Agile team or a team that is transitioning towards an Agile process.

git config alias.datetag '!git tag `date "+%Y%m%d%H%M"`'

a really really great way to use git from emacs

It's Magit! A Emacs mode for Git.

Git mode for emacs

Uma história para descrever o funcionamento interno do Git

simple, but extremely powerful system. Most people try to teach Git by demonstrating a few dozen commands and then yelling “tadaaaaa.” I believe this method is flawed. Such a treatment may leave you with the ability to use Git to perform simple tasks, but the Git commands will still feel like magical incantations. Doing anything out of the ordinary will be terrifying. Until you understand the concepts upon which Git is built, you’ll feel like a stranger in a foreign land.

"The following parable will take you on a journey through the creation of a Git-like system from the ground up. Understanding the concepts presented here will be the most valuable thing you can do to prepare yourself to harness the full power of Git. The concepts themselves are quite simple, but allow for an amazing wealth of functionality to spring into existence. Read this parable all the way through and you should have very little trouble mastering the various Git commands and wielding the awesome power that Git makes available to you."

'The following parable will take you on a journey through the creation of a Git-like system from the ground up.'

ability to push to and pull from a Git server repository from Hg

[extensions] hgext.bookmarks = hgext.hg-git = [path-to]/hg-git

"GitHub Firewall Install is a version of the GitHub web application that you install within your own corporate firewall. With your own internal GitHub you can combine the best aspects of social code management with the security of your private network."

overview of git features

http://www.ralfebert.de/blog/tools/visual_git_tutorial_1/

Extremely well written!

Scott Chacon's CC licensed book on Git.

st on the Pro Git book website, which contains the full content of the book published by Apress and a blog for me to share Git tips and book news with everybody.

hgsubversion installation guide

to rebase or to merge, that is the question.

intro to rebase

Rebase helps to cut up commits and slice them into any way that you want them served up, and placed exactly where you want them. You can actually rewrite history with this command, be it reordering commits, squashing them into bigger ones, or completely ignoring them if you so desire.

a result if Professor Plum is changing some code

Don’t rebase branches you have shared with another developer - they will hate you and you will hate yourself.

Quick, clear, simple guide to the way Mercurial handles branching.

Nifty program that visualizes changes made in a Git repository over time.

Gource is a software version control visualization for Git and CVS.

brose git repos mutt style

Git is pretty easy to get: on a Mac, it’s probably easiest to use the git-osx-installer. If you have MacPorts installed, you may want to get Git through it; you can find instructions on the GitHub help site. (And yes, we’ll talk about GitHub). On Windows, the simplest way to start rolling is to use the msysgit installer. However, if you’ve got Cygwin, you can git Git through there as w

Have you ever worked on a project that was so unwieldy, you were scared to update a file or add a feature? Maybe the problem was that you weren't using a

Inspiration for API for versioning XBRL instance document

gitは便利だな～

初歩の初歩

gitってコミットログの修正とかできるのか。てか普通出来るよね…(何

Version control (compatible with Mercurial) written in Ruby.

Mercurial ported to Ruby with very easy customization.

Amp is unlike any other VCS software to date. Amp's novel command system gives you the flexibility to customize and personalize the way you develop software. Create in your own workspace with full Mercurial compatibility, and no external dependencies.

Windows環境でSubversionによるバージョン管理を行いたい場合に便利なのが、GUIでリポジトリにアクセスできるTortoiseSVNだ。本記事では、TortoiseSVNの導入から基本的な使用方法までを解説する。

TortoiseSVNの使い方あれこれ

The GitTorrent Protocol (GTP) is a protocol for collaborative git repository distribution across the Internet.

It might currently come across as a solution looking for a problem - and as one smart-ass with admin rights to the Google Code project reminds you on the source tab, "more alpha than the greek letter". The initial motivation was performance of downloads and in particular reducing load on kernel.org.

This could be interesting.

Instead of contributing to the mass of tutorials already written about the subject, I figured I would take the easy useful way out and compose a list of great tutorials on how to accomplish a migration to Git for those who are familiar with SVN. If you have more links, please comment away and I’ll add them in.

Some tutorials and other resources related to migrating from SVN to Git

links on how to use git and svn together

About composing commits and writing commit log messages.

An opinion piece on what comprises a good commit message.

Any software project is a collaborative project. It has at least two developers, the original developer and the original developer a few weeks or months later when the train of thought has long left the station. This later self needs to reestablish the context of a particular piece of code each time a new bug occurs or a new feature needs to be implemented.

"In the last few weeks, I've had a surprising number of discussions about commit messages. Many of them were with developers new to a project, trying to get them started. So here's a list of things you should do when committing, and why you should do it."

An excellent list of best-practices for commit messages when using your favourite version control system.

good reasoning on howto, and hwo not to write commit messages

some day I need to read these things

There are obviously many reasons why Git is awesome (and why it sucks too), and there comes a point where it helps to dispel some of the rumors and issues surrounding Git. The following list attempts to show what Git is not.

git resource

SVNの使い方のポイント

Source Control HOWTO

Our universities often don't teach people how to do source control. We graduate with Computer Science degrees. We know more than we'll ever need to know about discrete math, artificial intelligence and the design of virtual memory systems. But many of us enter the workforce with no knowledge of how to use any of the basic tools of software development, including bug-tracking, unit testing, code coverage, source control, or even IDEs.

Beginners guide. Very good introduction.

starter for using a central git repo

Looks like the model we should use to start our migration away from svn.

http://malagma.org/wiki/

無料で使える Git のリポジトリサービス。 install したところで止まってて、まだ実用レベルに入れてないけど。

git diff --staged git log --oneline --graph

If you're not yet sportin' the 1.6.3 hotness, here are ten reasons to Git up!

This is the Git reference site. This is meant to be a quick reference for learning and remembering the most important and commonly used Git commands. The commands are organized into sections of the type of operation you may be trying to do, and will preset the common options and commands needed to accomplish these common tasks.