And if it's any consolation, it took me long enough to learn that myself. I always thought of "updating" something as pushing out my changes to long-term storage, but in version control, that's a commit and "update" is when other people's changes get pulled into your copy.
Or in short, it's you being updated, not the project repository.
Customer surveys are for companies who didn't pay proper attention to begin with.
With other words, an "update" gives you what has been "committed" by everyone else since your last "update".
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
manas ranjan mandal
Joined: Apr 02, 2008
What you have explained me till now i think its not enough for me to gave a clear idea about update and commit.can any one give me any good and practical example for this? Thanks in advance
I think Jesper's is pretty clear, but here's a little scenario.
I start a new project and need to create a new workspace so I check out the code from CVS. Then someone tells me about the project and I go home. The next morning, I update my workspace to get all the changes that have occurred the previous day. After all, I want to start with the latest code. I code/test the method assigned to me until lunch. I update my workspace again to make sure everything works with my change. Then I commit my change so others on the team can see it.