But look at my intention: On Mon, Feb 21, 2011 at 18:21, Christian Halstrick <christian.halstrick@xxxxxxxxx> wrote: > I would like to create such tags to mark released states of my sources > which should never be garbage collected in case no branch is pointing > them anymore. On the other hand these tags should not pollute the > namespace of normal tags, means: don't want a 'git tag' command to > list those technical tags. Is there any better way to achieve that certain commits are not garbage collected than to create such tags. I love my foot and don't want to "shoot if off" but I want to make sure the the "release-process-machinery" in our company can be sure that certain source states are never gc'ed. I can also live with creating normal tags 'refs/tags/release/1.20' but would prefer a solution where 'git tags' shows only developer created tags. Will any ref underneath "refs/' prevent gc to garbage collect a commit? Or only those in the well-known locations (e.g. refs/tags/*) -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html