Re: "bk pull" is not updating my local repository

Hello,

> But if I check in the files, then I have to supply all the comments
> for the changelog.  What if I'm not ready to do that?

The comment you suplly on bk ci is the comment for this delta.

Like 'introduced a variable (yet unused)'. After you have introduced a
new feature like 'implemented colorized status bar for mutt' you can
commit all this deltas into one changeset and name it appropiate.

You also have a chance to edit any comments later - Before you published
the comment.

> It seems odd that I need to check in files in order to pull other
> files.  I've used a dozen other version control systems, and that's
> never been a requirement.  I've always been able to get the latest
> version of any file whenever I want.

Bitkeeper works different and it wouldn't work together with one of
bitkeepers features (be atomar). It took me a very long time to learn
how to work in many small steps. I needed over a year on project work
(FAUmachine) to learn how to do it with cvs.

However on CVS the upstream changes are just merged in the edited files.
In bitkeeper you import a change and than there is a merge. The merge is
another changeset which is atomar again.

	Thomas
_______________________________________________
Bitkeeper-users mailing list
[email protected]
http://bitmover.com/mailman/listinfo/bitkeeper-users
To unsubscribe from this list, go to the above URL, follow instruction at the bottom of the web page.