On Wed, 25 Apr 2007, Andy Parkins wrote: > On Wednesday 2007, April 25, Julian Phillips wrote: > >> Why not create a directory .git/refs/bm and put things you don't want >> to make public in there? You can then use bm/foo etc ... > > I could, but then they don't get treated as tags properly in qgit. I > still want to list them in git-tag -l While I like the idea of private tags, I find the idea of them having their own namespace to be much more attractive than simply having the ability to not export lightweight tags. In particular it means that you can control which tags are exported individually. (You can also create a signed private tag, and then make it public at a later date - e.g. maybe a security fix that you have to sit on?) > >> You could even modify git-tag to create them for you with some >> appropriate switch ... > > Well yes, but that's the answer to everything isn't it? Not with closed source software ... :( The first of the following patches just changes do_one_ref so that passing a base with strlen(base) > trim is actually worthwhile. The second adds basic support for private tags (bookmarks). -- Julian --- Nothing is but what is not. - 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