I'm pretty sure that "Operation" has always been a battery-powered game.

Sent from my iPhone

And here's the real problem with Fox News. It subverts the very idea of there being an objective truth in order to push its agenda. Obama's birth certificate is publicly available, copies have been displayed in multiple news sources, but the Birthers always require "one more level" of proof. Hey, it could have been forged, etc, etc. At some point you have to accept secondary sources unless you're doing the research yourself.

Let's say you had a uncaught labelling error on a source file (foo.c) when you create your baseline label. I know, you're checking for that, but just for the sake of argument, let's say it happened. With a /main/LATEST catch-all rule, you would be getting whatever version of foo.c happens to be /main/LATEST. When you run a build, you may or may not get an error, but you run the risk of introducing a bizarre bug in your build image, which could lead to many hours of debugging before you track it down to that source file being the wrong version. With a /main/0 catch-all rule, you will most likely get a compile error (since foo.c will be empty). Maybe not when foo.o gets generated, but rather at link time. Basically, you're better set up to catch the problem sooner.

But yes, you are correct that it should be the same. Using /main/LATEST can also be nice if you have areas that are not labeled and you want to get /main/LATEST for those other ares.

element * CHECKEDOUT
element * .../branch/LATEST
element * BASELINE -mkbranch branch
element * /main/0 -mkbranch branch

Actually, you can. fire the contractors or give them other jobs, tear up the policies and protocols, issue a big mea culpa and move on.