Reply to post: There's a lot of thing Perforce just Won't Do

Splunk: Why we dumped Perforce for Atlassian's Bitbucket of Gits

Richard 12 Silver badge

There's a lot of thing Perforce just Won't Do

Like "Give me the full list of commit descriptions between labels X (new) and Y (old)"

You know, a core function of any source control system.

It's simple to get that for the current branch/stream, but actually impossible to get it to reliable include all merged branches/streams - you often get bits from before Y, and sometimes everything that has ever happened ever.

After four months of trying I finally got something that almost works, but not quite.

It means the automated build reports are rarely correct - and that is very scary.

In short, Perforce is a very poor tool for management of code history.

On top of that, it can't deal with line endings in a sane way, it can't show you the history of what got imported from other projects (it's apparently there but impossible to see in any way)... the list goes on.

In short, Perforce is a very poor tool.

I would say that git is at least a decade ahead, and that Perforce will never catch up.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon

Biting the hand that feeds IT © 1998–2021