git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: git@vger.kernel.org
Subject: git top links: 2010-2
Date: Sat, 13 Mar 2010 19:35:36 +0200	[thread overview]
Message-ID: <94a0d4531003130935wc557eaare5d4103233e6de65@mail.gmail.com> (raw)

Hi,

git top links is my attempt to gather all the links people have been
tagging as "git" in delicious.com[1] (these are not chosen by me).

The fancier blog version is here:
http://gitlog.wordpress.com/2010/03/13/git-top-links-2010-2/

1. A Visual Git Reference (125)
Very nice visualizations of common git operations
http://marklodato.github.com/visual-git-guide/

2. A successful Git branching model (45)
http://nvie.com/git-model

3. Aha! Moments When Learning Git (43)
Explanation of commonly ignored git concepts
http://betterexplained.com/articles/aha-moments-when-learning-git/

4. 分散バージョン管理入門 (イラスト入り) (18)
http://tcha.org/2010/intro-to-distributed-version-control-illustrated/

5. Smart HTTP Transport (13)
Excellent explanation of the apparently underhyped http transport
http://progit.org/2010/03/04/smart-http.html

6. Only You Can Prevent git Merge Commits (10)
Simple tip to avoid merge commits
http://www.viget.com/extend/only-you-can-prevent-git-merge-commits/

7. Setting up a public (bare) repository with git (9)
http://www.onyxbits.de/content/setting-public-repository-git

8. Git for Eclipse users (9)
http://alblue.blogspot.com/2010/02/git-for-eclipse-users.html

9. 10 Useful git commands (8)
http://about.digg.com/blog/10-useful-git-commands

10. 私がSubversionをやめてGitに移った理由 (6)
http://journal.mycom.co.jp/news/2010/03/09/014/index.html

[1] http://delicious.com/tag/git

-- 
Felipe Contreras

                 reply	other threads:[~2010-03-13 17:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=94a0d4531003130935wc557eaare5d4103233e6de65@mail.gmail.com \
    --to=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).