Using git as article storage?

[Fredrik Unger <fred@tree.se>]

Hi,

I have been using git for various projects and also as a backend for
storing docbook xml articles.

My pool of articles have grown and I now have the problems of revisions.
I would like to tag the revisions to at some point at least be able to
easily go back and look at an earlier version.

If you use git in a similar way, how do you deal with tagging revisions?

I would like a "local" tag, which would be possible with svn in moving
the wanted files into a own tag directory.

If I use the global tag I need to specify the path to the files somehow,
or I can not have a revision 1.0 of two articles.

I have asked on irc at #git@freenode and have gotten several answers :
- You are doing it the wrong way, git is no CMS
- Use the log messages to note Revision
- Make one git per article, see https://gist.github.com/gists does that.
  (I have no such automated git generation just, and setting up a git
   is some work http://article.tree.se/tools/git/https )

Now non of the answers were really satisfactory and I would just like
to know how you deal with your documents if you use git.

Would be grateful for any comment. It is an unusual case as the articles
are small and not really mandates an own git as a book would do.
Like using a git for a bunch of smaller scripts or code snippets..

Sincerely,

Fredrik Unger