You figured it out. Current change set is a way to denote the prefered
change set to check new files into, when using the "Check in All" action.
But changes to files always go into opened change sets that modify that
same file first.

I find this behaviour useful if I'm working on two independent bugs and
I'm too lazy to suspend/resume. I know I just need to get the right files
into the right change sets the first time around (by setting Current to
the change set according to which bug I'm working on), but after that I
can just use "Check in All" and the changes collect in their appropriate
change set when I'm only modifying files I've already edited before.

On Fri, 07 Aug 2009 07:08:03 -0400, David.Sedlock.infineon.com
<David> wrote:

When I try to explicitly checkin against the 2nd changeset, I get the
msg "cannot checkin because file is being changed in another
active changeset". But the 2nd changeset is clearly marked as
current!

OK, I found it:

Note: A file or folder in a component cannot be part of more than one
active change set. When a file or folder is included in an active
change set, all changes to it become part of that change set whether
or not the change set is current, and changes to that file or folder
cannot be explicitly checked in to a new change set until the active
change set that includes it is completed.

So, despite the fact that a different changeset is current, if I
continue to change a file that has already been changed against some
other changeset, the changes continue to be charged to it until it is
completed. If I were to change a different file, which was not in the
first change set, the changes would go into the current one.

I can understand the reasons behind this, but probably some extra care
is needed - e.g. a message that the current changeset is not being
used because of this rule.

--

The key here is the use of "checkin-all".

Here's what's happening.
You cannot checkin a change to a given file to a new change set if you
have a checkin to that same file in a non-completed change set.

If you had explicitly tried to checkin to the new change set, it would
have given you an error message of the form "you cannot checkin to this
change set because you have a non-completed change in another change set".

But for checkin-all, for any given change, it first looks at whether you
have a non-completed change set with changes to that file, and if so,
checks in to that change set. Only if you do not have such a change-set
does it look to see what the "current" change set is.

So you need to "complete" the first change set before you can checkin to
the second change set.

Cheers,
Geoff

David.Sedlock.infineon.com wrote:

I did it all carefully again and it really is not working.

"auto-checkin" is NOT on.

I used "checkin-all" operation with the Unresolved folder
selected.

I carefully ensured that the 2nd changeset was marked as default. This
showed up clearly in the GUI.

The 2nd change is clearly associated with the 1st changeset. The
history of the file does NOT show the 2nd changeset. And the 2nd
changeset shows no files associated with it in the ChangeExplorer.
Suspending the 1st changeset backs out both changes.