Preserving branches after merging on ancestor

Hello gits,

I've been using various version control systems for several years now before coming to git two months ago. So far I've been just doing linear commits without any branches on my source code so that I end up with a linear history. This makes it very hard to see where you started and stopped working on something on the git graph.

So I tried using branches for features today. Most of the time I'm the only person working on a project. So when I've finished working on a feature branch and ready to merge it back into the master branch, the master head IS the common ancestor of the two branches. As shown below

* b6d75f1 [feature] stuff on feature branch
* 43dba08 stuff on feature branch
* ab7efdd [master] init

When I merge the graph looks likes this:

* b6d75f1 [master] [feature] stuff on feature branch
* 43dba08 stuff on feature branch
* ab7efdd init

Now I lose the start point of where I satrted on the feature branch. And if I decided to reuse the name of the branch 'feature' to work on it again by resetting it to somewhere else, I loose to finish point. (Should I be using git-reset like this?)

One way of getting round this problem is to use empty commits on the master branch, as shown below.

*   6fc04b5 Merge branch 'feature2'
|\
| * 07a117b stuff on feature2
* | 52f5ba1 Empty commit
|/
*   5deaa93 Merge branch 'feature1'
|\
| * b163b17 stuff on feature1
| * 53bb820 stuff on feature1
| * c9ef14c stuff on feature1
* | 34227a3 Empty commit
|/
* e88d332 Init

But is this correct? It seems rather hackish to create empty commits on the master branch just to historically preserve commits on a seperate branch. Should I be using feature branches in git like this or another way? For example more informative commit messages.

I cannot imagine using this empty commits fix in other VCS if they don't allow empty commits like svn or hg.

Cheers,

Richard