Re: git push tags
- From
- Angelo Borsotti <angelo.borsotti@gmail.com>
- Date
- Oct 26, 2012, 06:42 UTC
- Message-ID
- <CAB9Jk9ApdbN+4Yk-6+u4Nje9+tbESSGGVj95iof1jnfG4Ga7GA@mail.gmail.com>
- In-Reply-To
- <CAM9Z-nkosbe1NXYnu7x6v4seLqCnMBWg-jrdH2eJ9RetaZBTyQ@mail.gmail.com>
Hi Drew,
Show 6 quoted lines
> > Changing the tag in the local repository is a tag modification > operation. Pushing that change to a remote repository DOES NOT execute > "git tag...." in the remote. Plain and simple the two are different > operations. >
They are different for what concerns the implementation. They are not necessarily so for what concerns their semantics, and the most straightforward is to apply to the remote repository the changes done on the local one -- the changes that can legally done on it -- and changing a tag is not one allowed (unless forced). Obviously, the semantics of git-push is different, and then needs to be described clearly. Note that some (probably most) of the operations that are disallowed on the local repo are also disallowed by git-push, like, e.g. deleting the current branch. But the user cannot tell what is disallowed and what not if the man page does not state it.
Show 7 quoted lines
> So here we come to the core argument. Is sounds to me like you want > changes to remote tags to work differently from push updates to ALL > other references. The required change, if I'm not mistaken, would be > for tags to not permit fast-forward updates while all other references > would be pushed normally. From my brief and un-enlightened look at the > push code I can't see that being as easy as it sounds. >
No, I was hoping that git-push refused to change tags at all, unless forced (e.g. prefixing them with +), as it is on a local repository.
-Angelo