First things first. Let's try and pull changes from our parent to make sure we have the latest code. A clone will automatically pull the latest revision of the code, and we haven't made any changes to our parent, but we're going to do it anyway just to see what it looks like.

Right-click on the bk_demo_copy folder. Click BitKeeper -> Pull Changesets from Parent.

A dialog will popup asking where we want to pull from. It will populate with the value of our parent repo by default, and that's where we want to pull from, so we'll just leave that in there.

Click the OK button.

Another command window will pop open and try to pull any new changes from our parent. In this case it won't find anything because we haven't made any changes in the parent. Close the command window, and let's try and pull changes from another parent that does have some changes in it.

Right-click on the bk_demo_copy folder. Click BitKeeper -> Pull Changesets from Parent. For Target URL use: http://bkdemo.bkbits.net/bk_demo1 Click the OK button.

You should see another command window pop up as BitKeeper pulls any changes from that repository. This time we should see some changes come through. Specifically, we see that a change has been made to e2fsck/region.c. You will see some other stuff in the command window that gives you a little more information about what just happened. The window should look like this, but it may not match exactly what you see:

If we look at this a little closer, BitKeeper is telling us what just happened. We see that BK is pulling two files: ChangeSet and e2fsck/region.c. The ChangeSet file is a file you will see with every change. It is the main file that tracks change sets within BK, and it is updated each time a change is committed. The second file is our actual code change. We see BK run the resolver and apply our changes to the changed files and then run a consistency check to make sure that data integrity is correct.