Subject: Expiring Soon: Ref Id 15-3771

From: Medicare Specialists <[email-masked]>
Date: Tue, 19 Aug 2014 10:12:19 -0700

Did you learn the hard way that Medicare doesn't cover everything?

Trying to figure out how your going to pay the difference?

A plan that fits your budget has been generated for you. 

View Details for Atompub-archive
[Ref Id No. 15-85224]
Generated: August 19, 2014

Policy Details: http://www.phobiaos.com/medicare/index/policygov.html

[Medicare Supplement and Advantage Plans | Part D Drug Plans (PDP) | Advantage Prescription Drug Plan (MAPD)]

/
/
/
To stop further notifications Daily Updated Alerts
nine three zero six - B O V A CT
Louisville, KY 40291 or visit http://www.phobiaos.com/56u/w3qwe.mji7yr
/
/
/
Missing a crucial point: If the said commit was previously 'pushed' to the remote, any 'undo' operation, no matter how simple, will cause enormous pain and suffering to the rest of the users who have this commit in their local copy, when they do a 'git pull' in the future. So, if the commit was already 'pushed', do this instead:  it won't cause "enormous pain and suffering." I've done a few force pushes when using Git with a team. All it takes is communication. In my workplace, messing up entire team's workflow and then telling them is not called 'communication'. git history re-write is a destructive operation that results in trashing of parts of the repo. Insisting on its use, while clear and safe alternatives are available is simply irresponsible.  I wouldn't call that communication either. Git is like the C language; it gives you a lot of power and expects you to be responsible with it. If people don't know how to be responsible, or refuse to be, then things will be awkward. The n
 ice thing about Git, though, is that you can't really trash the whole team's repo, because everyone has the repo. In a centralized repository, if you roll back some changes, nobody can get , I have a question about your answer. You say that "git reset --soft" "not only leaves your files alone, it even leaves your index alone. When you do git status, you'll see that the same files are in the index as before. In fact, right after this command, you could do git commit and you'd be redoing the same commit you just had." But if "git reset --soft" doesn't change the index, "git commit" wouldn't do anything. Do you mean  perhaps one way to look at it is that there are three things working here: Your files, your index, and your history (that is, your branch pointer). Let's say you're at commit C (as above). Your files, index, and branch pointer match. If you use git reset --soft HEAD~1, your branch pointer moves back to B, but your files and index stay at their versions in C. If you use git
  reset --mixed HEAD~1, your branch pointer and index move back to B, but your files stay in their state at C. Then your files show changes but your index doesn't. git reset --hard HEAD~1 moves all three back. 
@Kyralessa, thanks so much for the quick reply. When I woke up, I realized what I was missing. I assumed that the index is empty when everything is committed, but now I understand it's a copy.   espertus Feb 20 at 16:08