I was reading the site builders guide to Git (http://drupal.org/node/803746) and had a question about renaming remotes across all environments. The guide indicates to only rename the remote on your local development environment to point to your new repository.
When I update/commit/push to my new repository everything is fine, but when I pull to my development or staging environment and run git status, I get a notice that my branch is ahead of origin/xxxxxxx by 3 commits.
Should I rename the remotes in all environments to point to my repository as origin??
I left a comment on http://drupal.org/node/803746#comment-4418628 basically asking the same thing. If I can get an answer from gdo, I'll update my comment there as well, or vice versa.

Comments
Nevermind
After running git remote -v it shows that the origin (in terms of the development, staging environments) is pointing to the right repository. That solves one issue, the other is: do I need to worry if my development/staging environments say that they're ahead by x number of commits?
And to finish my one person convo
The "your branch is ahead by x number of commits" disappeared after I did another git pull. LFMF!
With all that being said, if you haven't read this post: http://drupal.org/node/803746 - it outlines how to get a properly tracked project going with git and drupal (despite my own ineptitude) ; )