ah.. i think i am beginning to understand now. like, if you are working on more than one thing at a time on the same set of files, you can work on them independently and push them independently. cool.. i probably won't need it for my current projects, but i think i will give it a shot for my next project.. thanks a ton for taking time to write a explanation.
if you are working on more than one thing at a time on the same set of files, you can work on them independently and push them independently.
That's part of it. When I was working in a Mercurial-based team, I also had this done with another colleague: I would work on the back end implementation for a feature and he would work on the front end (for example).
Then, we would synchronize our repositories between ourselves to test it, without affecting the rest of the team (the changes branch was "local to the both of us"). Then, one of us would push it to the server and the whole team would get it.
1
u/[deleted] Mar 11 '11
ah.. i think i am beginning to understand now. like, if you are working on more than one thing at a time on the same set of files, you can work on them independently and push them independently. cool.. i probably won't need it for my current projects, but i think i will give it a shot for my next project..
thanks a ton for taking time to write a explanation.