|
|
|
Checking in changes
Checking in files and creating a changeset can be done via the command line
or with bk citool, the graphical check-in tool.
We recommend using bk citool because it shows the changes
made to each file which improves the quality of the comments.
Steps for the graphical tool are shown first followed by steps for another
file edit and the command-line check-in.
Using bk citool:
 |
bk citool
|
 |
Add comments about the changes in the middle window.
Click on the icon next to foo.c to add this file to the repository.
Click on ChangeSet.
Add comments about the ChangeSet in the middle window.
Click on the Commit box at the right.
Click on the Commit box again to confirm you are done.
|
You have now checked in your changes, added the new file foo.c, and
grouped these changes into a changeset. Next you will check in changes
using the command line:
|
echo foo > bar.c
bk new bar.c
bk edit foo.c
echo "This is file foo.c" >> foo.c
bk ci -y"These are the checkin comments" foo.c
bk commit -y"These are the changeset comments"
|
To see the changes you've just made:
|
bk revtool
|
|
Double-click on the box containing "your_login 1.125".
In the bottom window, click on the line under "e2fsck/recovery.c".
|
The history of the recovery.c file is shown in another bk revtool
window. You can use bk revtool on files in the same way you can use it on
a repository.
|
Click Quit in all BitKeeper windows.
|
| |
|
Home 
Test drive