Hi, you may have noticed the yellow tags on http://git.opensuse.org/?p=projects/yast/rest-service.git;a=summary They are actually quite more useful than on SVN. HARVEST ------- Here's how it helps me write the changelog cd .../rest-service/plugins/services git shortlog yast2-webservice-services-0.0.1..yast2-webservice-services-0.0.3 . Ladislav Slezak (1): all REST plugins - added .gitignore files Martin Vidner (6): Lsbservice: less clutter, small refactoring. Fixed mocking a bit. Be lazier: /services no longer includes command info. Redirect the other way around Removed %config 0.0.3 Stefan Schubert (1): changed licences That's git shortlog TAG1..TAG2 PATH TAG2 will usually be HEAD, and for TAG1, tab completion works. Cool, huh? PATH limits the log to my subtree of the repository. Use "log" or "diff" instead of "shortlog" to get the obvious variations. SOWING ------ The simplest form creates the tag on HEAD: git tag yast2-webservice-language-0.0.42 For consistency, I recommend the form $RPMNAME-$VERSION It just makes a label for a commit (ls .git/refs/tags/), like on CVS and unlike on SVN. There are also another kinds of tags in git, "tag objects", but I haven't used those. A catch is that pushing normally keeps the tags private. You need to remind git to make them public: git push --tags Once you push a tag out, it is hard to get rid of it if you got it wrong. See "On Re-tagging" in man git-tag and browse our repos for some examples ;-) -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org