On Thu, Dec 20, 2007 at 02:05:24AM -0800, MattyJ wrote:
We've cut out the use of labels (at least from a CM perspective) and solely use branch/changelist combos, pretty much for that reason. That's really the only concrete, unchanging way to refer to a version of a file in Perforce. Also, since the owner of a label can move it at any time it's not 100% trustworthy.
Of course, label abuse is nothing compared to how client specs can be abused in P4. I had to work on one project that had over 1,000 lines in its client spec. The big problem is that the client spec isn't revision controlled in any way. So, the CRM management people end up making a copy of a whole client spec to go with every version they label (so it would actually be possible to get the state of the files in the old version). Plus, I think they still don't trust it, since there is also a massive network store that holds a complete expanded tree copy of every released version. That's even less pleasant to use, since it has absolutely no history. Dave -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
