Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm not exactly sure how I got myself into this situation, but essentially, I had modified an existing codebase and added some new files and few months back, and when I went to check it in, I created a new tag and committed. That worked fine.

Fast forward to now, when I found a bug in the old code. I fixed it, and committed, thinking that the tag would be updated to point to the updated revisions. It wasn't. I then tried using rtag, and it worked for some, but not all of the files I modified. Is there any way to take the exisiting tag and just have it point to the new revisions of the files?

share|improve this question

You must log in to answer this question.

Browse other questions tagged .