Add another FAQ.
diff --git a/README.mdown b/README.mdown
index 4b56580..7fe03c9 100644
--- a/README.mdown
+++ b/README.mdown
@@ -70,6 +70,33 @@
a problem. As long as you do it conciously and realize what this means for
finishing those branches later on.
+* **Why does git-describe not work for me?**
+ When finishing release and hotfix branches, that branch's HEAD is first
+ merged into `master` and then into `develop`. It is not the resulting new
+ merge commit from `master` that is merged back into `develop`. This means
+ that a linear path from the new `develop` branch to the new `master` commit
+ is not created. Even worse, a linear path is created from the new `develop`
+ branch to the *previous* `master` commit. Although unintended, this is
+ simply an effect of using the current branching rules.
+
+ When using `git-describe` in these cases, you can get very confusing and
+ misleading results, since `git-describe` scans the current commits linear
+ history for the most recent tag it finds, which will always be the *previous*
+ tag.
+
+ I will change this behaviour in the next version of the branching model
+ explicitly and I will include this behavioural change in the first version of
+ the Python rewrite.
+
+ For more references to this problem, see:
+
+ - Issue [#49](http://github.com/nvie/gitflow/issues/49)
+ - These
+ [two](http://groups.google.com/group/gitflow-users/browse\_thread/thread/9920a7df3d1c4908/0bb18a0bf7275ad6#0bb18a0bf7275ad6)
+ [discussions](http://groups.google.com/group/gitflow-users/browse\_thread/thread/19efac724bb6418a)
+ on the [git-flow-users](http://groups.google.com/group/gitflow-users)
+ mailinglist.
+
* **I'm getting errors when I use flags with git-flow!**
`git-flow` uses the [shFlags](http://code.google.com/p/shflags/) library to
provide platform independent flag parsing (using wichever low-level flag