Nicholas,
Anyone who hates perforce is a victim of bad education or software religion.
It's faster, it's safer, it's lighter. It just works.
Reverts too difficult for you? Then don't revert changes. Use the software how
it's meant to be used. In a live perforce install for twenty developers I saw
fewer than three reverts in three years. Guess what, these were not legendary
perfect developers. They just used p4 sensibly and as intended.
Neil.
On 27 Jan 2011, at 07:01, Nicholas Clark <[email protected]> wrote:
On Thu, Jan 27, 2011 at 01:55:34PM +1030, Martin Ebourne wrote:
http://kb.perforce.com/article/14
Yes the version control system that needs an entire chapter on how to
revert a change, with multiple different possibilities depending how old
the change is or whether it included new/deleted files, and up to 9
commands per revert. How can that be right? Of course it misses out
reverting a change from a branch where that change was committed before
the branch was taken. Why? Well because in that case you can toss
perforce out, you'll be needing good old diff and patch (which tbh is a
better choice anyway). I've probably posted that article to this list
before, but it is a cauldron of hate so I make no apologies for any
repetition.
Strangely, I thought I had hated that here. But I can't find any reference
to it.
Anyway, amen brother. The attitude that results in that kb existing at all
is one of my big hates about perforce.
Nicholas Clark
