On 1/17/07, Alberto SAVIOTTI <email@example.com> wrote:
> Project scenario:
> TRUNK with Revision "1".
> Action A:
> Create branch_1 and change a file: Revision "2" is created on the
> Action B:
> On the TRUNK update to Revision "2" (that doesn't exist on TRUNK).
> The action is performed.
> Now I'm on TRUNK and Revision "2" for the whole project is displayed.
> Action C:
> On the TRUNK update to Revision "3" (that doesn't exist). The action
> is refused.
> I think that Action B shall behave as action C. I verify this with
> command line and with SmartCVS. With SmartCVS the Revision "2" doesn't
> appear in the Revision history for the TRUNK but the update can be forced
> writing directly "2" in the update window.
> If I'm wrong and this is not a bug please explain because is quite scary
> and is the only concern in order to switch to SUBVERSION our CVS
Revisions are for the entire repository, not specific folders. When you
commit something, the revision of the entire repository is bumped up by
one. For unaffected paths, it just so happens that there is no difference
between those revisions, but those paths do have a representation for each
revision. This is explained well in the book:
I have a blog entry that is also somewhat relevant to this and might help
Received on Wed Jan 17 16:12:33 2007