A baseline has two aspects ...
- it is a set of versions. In this aspect it is not something that can
be accepted or delivered ... but it is something you can use to
"replace" a given configuration to get the configuration specified by
the baseline.
- it is the result of a series of change sets. In this aspect, it is
something that you can accept, and it implies that you are accepting the
set of change sets leading up to that baseline. But it also implies
that you are accepting the baseline itself (so that it shows up in the
history of the stream).

Note: I personally would only give a baseline the first aspect, because
I believe giving it both of these aspects, although useful at times,
produces more confusion than benefit. For example, you have that
"accepting a baseline with no change sets" situation that you
encountered. It's even worse when parallel development has occurred
with baselines being created in both the stream and the workspace ...
when accepting a baseline from the stream, both the incompatible
baselines from both the stream and the workspace cannot appear in the
workspace history, so one will disappear. I would prefer to handle
baselines just the way we handle snapshots ... which only have aspect
one, and not aspect two. Work item 85458 requests this change ...
please feel free to add a comment to that work item to indicate your
interest/support.

Cheers,
Geoff

On 11/29/2011 4:38 AM, ulricheckhardt wrote:

Hi!

I've been wondering, what is the meaning of this? I was under the
impression that baselines are "global" and not something
you could accept or deliver, because they just "are". The
Eclipse RTC client seems to confirm this to some extent, because I
also can't suspend or discard a baseline. However, I still have
baselines in incoming and outgoing sections of the "Pending
Changes" view, which suggests that I can do something with
them.

Note that I understand that if a baseline tops off a bunch of incoming
changes that I can accept the baseline in lieu of those changesets,
but I'm talking specifically about empty baselines.

Thank you!

Uli

If you don't want to see these baselines, there's a preference for Pending Changes to show all baselines. If you uncheck this, it will hide empty baselines.

 I have a related inquiry,  although I've learned (through experience) some of the behaviors regarding accepting (and delivering) baselines. Like when multiple baselines are accepted or delivered only the latest is "associated" with the target.  Specifically I'm looking for any documentation I can reference to our user communities that speaks to behaviors like that for baselines.  Appreciate any articles/info you can share.