Most people probably already know that it’s possible to merge histories of multiple repositories by using the subtree merge strategy [1]. However, sometimes you also need to separate/decouple the history of a repository’s subdirectory into a stand-alone repository. This post outlines how.
git status and other commands display utf-8 filenames containing umlauts (äö etc) differently from the shell, eg. as escaped (\266, \303 etc). So in case you are having problems with umlauts, the following command should help:
$ git config core.quotepath false
From man git-config(1) for core.quotepath:
The commands that output paths (e.g. ls-files, diff), when not
given the -z option, will quote “unusual” characters in the
pathname by enclosing the pathname in a double-quote pair and with
backslashes the same way strings in C source code are quoted. If
this variable is set to false, the bytes higher than 0×80 are not
quoted but output as verbatim. Note that double quote, backslash
and control characters are always quoted without -z regardless of
the setting of this variable.
I have to admit the more I use git the more I love it. Here are some random tips of commands I have found useful.
I needed a nifty way of changing author name/e-mail in multiple commits when someone made commits with wrong authorship details.
The orig branch here contains the commits to be modified, and rewrite will contain the rewritten commits.
git checkout -b rewrite git reset --hard HEAD~4 # last four commits git format-patch --stdout HEAD..orig | sed 's/^From: Joe <foo@bar>/From: New <new@mail>/' > mbox git am mbox
Stanislav found another way to change author of git commits, but I prefer mine. 
git checkout -b rewrite
Finally. About time – this has been requested several times since 2006 or so.
The announcement: Git now available for SF.net hosted projects.
Interestingly, the features page mentions that there is no quota. In that sense, SourceForge seems to be better off than other git services that have a “soft” quota (repo.or.cz has 100 MB for example).
Some pros/cons:
After two months of development, ViewGit has now been publicly registered and released -after wrestling SourceForge for 3 days until the website area was created. 
ViewGit is a git web repository viewer that aims to be easy to set up and upgrade, light on dependencies, and comfortable to use.
Freshmeat announcement is pending (project page). I’ve also posted links to the project homepage at GitWiki Gitweb page, ViewSVN homepage, and ViewSVN news. It’ll be interesting to see how much exposure the project will garner (if any – GitStats certainly didn’t get much, I have received mail from two users regarding it. Oh, and there was a RFP (Request For Package) for Debian, which was promptly dropped with a claim that “upstream seems to be inactive” (AIEEE!).
Visit the homepage for more information and further links. 
Since getting more famialiar with git (the version control system) over last year, I have started increasingly favoring git for my own projects (over, or side-by-side with Subversion (SVN)). This post explains some reasons why.
GitStats has been registered as a project on SourceForge.net now. See the examples for uh… well, examples of what it can do
