On Fri, 2 Feb 2007, Jakub Narebski wrote:
Well, in git you can have private tags (anything not under refs/tags
or under refs/heads is by default private), but I think you can only
have not published branches (which are not pushed to public repository).
If it is not true, then how one can have private branches
(i.e. branches which 'push --all' would not push)?
I have private branches, I just don't push them. The same thing is true of
tags.
Anybody who actually publishes his own git directory *directly* to pthers
is probably insane. It's like showing your home directory. You just
shouldn't do it. So anything in a real development archive is - by
definition - "private". Only when you actually expose it explicitly (by
exporting it at some public place) do things become public.
But if you tie your tags to history, you *have* to push them as you push
the history.
So again, this is not about private vs public. The bug is not there. The
bug is thinking that you should make tags part of your history.
Linus