Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Perforce introduces GitSwarm

perforce.com

Post reply on HN
Print view View original

21–30 of 37 posts

Re: Perforce introduces GitSwarm

#21

Post by dahart »

Tuna-Fish wrote: post #12
dahart wrote: post #7

Earlier quoted context omitted.

I had the same skeptical question in my head while reading the landing page / ad. But, I will say I super miss P4's 'timeline'. I haven't used Perforce tools for many years now, but last time I did it was way way easier & faster to figure out who wrote a line of code than it is in git today. And overall, the UI was much better then than any git based UI is today. So, it might be hard for them to explain to git users,…

> it was way way easier & faster to figure out who wrote a line of code than it is in git today. Don't you have git blame integration in your editor?

I do, and it doesn't hold even 1 candela to P4's timeline. ;)

Re: Perforce introduces GitSwarm

#22

Post by jscahefer »

Lets take it as a given that you are excited about becoming a poweruser of the perforce ecosystem (hey, if my complany chose this tool, the least I can do is understand it very, very well), documentation resources are lacking I.M.O.

very few up to date third party books, the video tutorials hang while you watch them, the documentation instructs you to press buttons that simply aren't there in the GUI. with no alternates give.

we paid for professional training and the answer given in the meeting was "experiment and see how it's working".

Uh, really?

Re: Perforce introduces GitSwarm

#24

Post by twk3 »

jscahefer wrote: post #22

Lets take it as a given that you are excited about becoming a poweruser of the perforce ecosystem (hey, if my complany chose this tool, the least I can do is understand it very, very well), documentation resources are lacking I.M.O. very few up to date third party books, the video tutorials hang while you watch them, the documentation instructs you to press buttons that simply aren't there in the GUI. with no alterna…

We recently heard that we were giving out links to GitLab's documentation instead of our own, (which we didn't have up on our website at the time.) We have since thrown them up here: http://www.perforce.com/perforce/doc.current/manuals/gitswar...

Re: Perforce introduces GitSwarm

#25

Post by kazinator »

brianwawok wrote: post #19
Tuna-Fish wrote: post #12

Earlier quoted context omitted.

> it was way way easier & faster to figure out who wrote a line of code than it is in git today. Don't you have git blame integration in your editor?

Git blame will often get the guy who fixed a spelling mistake in a variable, not the guy before him who wrote the code.

To continue digging previous history:

   git blame ^ -- file.c
Where is the hash of the commit where the spelling mistake was made, pulled from the original blame from HEAD.

Though I don't use such stuff, I would be surprised if there wasn't IDE support to make this "deeper dig" more of a point and click operation.

Re: Perforce introduces GitSwarm

#26

Post by sytse »

vvanders wrote: post #13
Roboprog wrote: post #2

What value does this add, other than perhaps supporting a proprietary build & deploy system already paid for built around Perforce??? (is the latter a feature, or a bug?) Every commercial revision control system I have ever used (ClearCase; SourceSafe; MKS Source Integrity; Serena VM aka PVCS) has always been much more of a PITA than CVS / SVN / Git. So, yeah, I'm very skeptical.

Looks like it has integration with an existing P4 server. There's quite a few teams(GameDev+Movies) who use P4 for scale+locking for binary assets where exposing a git endpoint would be useful from a tooling perspective.

This is spot on. Perforce can handle enormous monorepos with all the code and binary assets of an organization. For those we're very glad that this gives them the option to use our GitLab.

Re: Perforce introduces GitSwarm

#27

Post by sytse »

JoshTriplett wrote: post #18
baconner wrote: post #6

First tfs, now perforce. The prevalence of git is clearly putting a lot of pressure on "enterprise" source control systems. It makes a lot of sense to just co-opt it and pull it into the rest of their ecosystem. At my org we've been trying to move towards an oss style pull request flow for tools and infrastructure projects but meeting a little resistance because "not enterprise." Getting that workflow into one of the…

> At my org we've been trying to move towards an oss style pull request flow for tools and infrastructure projects but meeting a little resistance because "not enterprise." I'd love to know what 'because "not enterprise"' means in your case. Resistance to a model without exclusive locks? Resistance to a non-centralized model? Support questions?

I would love to know as well. We offer GitLab Enterprise Edition so our naming already is compatible.

Re: Perforce introduces GitSwarm

#29

Post by vetrom »

kazinator wrote: post #25
brianwawok wrote: post #19

Earlier quoted context omitted.

Git blame will often get the guy who fixed a spelling mistake in a variable, not the guy before him who wrote the code.

To continue digging previous history: git blame ^ -- file.c Where is the hash of the commit where the spelling mistake was made, pulled from the original blame from HEAD. Though I don't use such stuff, I would be surprised if there wasn't IDE support to make this "deeper dig" more of a point and click operation.

There is, try `git gui blame`.

Re: Perforce introduces GitSwarm

#30

Post by cynoclast »

Roboprog wrote: post #2

What value does this add, other than perhaps supporting a proprietary build & deploy system already paid for built around Perforce??? (is the latter a feature, or a bug?) Every commercial revision control system I have ever used (ClearCase; SourceSafe; MKS Source Integrity; Serena VM aka PVCS) has always been much more of a PITA than CVS / SVN / Git. So, yeah, I'm very skeptical.

Nailed it. You know what Perforce is? An overcomplicated, shittier version of SVN that's harder to use, and uses a bunch of the wrong words to describe thing so as to separate it from SVN and boost vendor lock-in.

Git is hard to understand for someone used to CVS/SVN, but it's better than both in the and, and completely free.

Post reply on HN