On Mon, Nov 23, 2015 at 1:24 PM, Bob Brodt <bbr...@redhat.com> wrote:
> Hi all, > > I need to "move" a tag to include the most commit, so I first tried this: > Something you want to be careful about. When you force push a branch, on the next pull everybody finds out about it via the discrepancy between branch and origin/branch. But I think if you force change a tag, everybody that has already pulled that tag will keep the old version. Git won't auto-update an existing tag in a local repo. Now it might not be a problem if you don't have a lot of contributors pulling your repo frequently, but you should make them aware on your *-dev list. If they delete the tag and pull again, they'll get the correct tag. Later, Paul -- Paul Webster Hi floor. Make me a sammich! - GIR
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
