On Tue, Feb 22, 2011 at 1:17 AM, Christian Halstrick <christian.halstrick@xxxxxxxxx> wrote: > 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. Yes, I'm sorry I wasn't more careful/clearer in my earlier reply. > Will any ref underneath "refs/' prevent gc to garbage collect a > commit? Or only those in the well-known locations (e.g. refs/tags/*) Anything under refs/ is safe, but you should create a subdirectory so that you've got your own name-space under there. For example, the gerrit code review system uses refs/changes/ for its refs. Because these refs would be outside git's normal name-spaces (refs/heads and refs/tags), they won't be fetched by the default (non-mirror) refspec. j. -- 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