News for hackers. Stuff that matters.
Re:Software Engineering at Google by jeffbee on Monday August 14, 2023 @12:45PM (#37123182)
Yeah, there are no direct translations between git and perforce concepts. The right term within Google would in fact be "pre-submit" not "pre-commit". Before a change is submitted in the Perforce-derived flow it exists only in the author's client and isn't really part of source control in the way that git users are accustomed to pushing their branch to origin.

NB: At that company there are also users of git-compatible and hg-compatible tools, but I am discussing the main perforce-derived flow.

Re:Software Engineering at Google by dinvlad on Monday August 14, 2023 @12:50PM (#37123272)
Oh I see, thanks! I was under impression Google has migrated away from Perforce towards an in-house system a while ago, but looks like I was mistaken (or do you mean that system is derived from Perforce?). Edit: I guess its name is Piper..

It’s quite interesting/mind-bending to think of work-in-progress that’s still somehow synced between peers (in fact this is one of those “missing nice-to-haves” I wish Git had, and can only be approximated with wip branches..)

Re:Software Engineering at Google by jeffbee on Monday August 14, 2023 @01:03PM (#37123488)
The synced-between-peers features are built atop a thing call CitC, or Client in the Cloud. An author's client isn't on their machine, it's hosted in prod.
Re:Software Engineering at Google by dinvlad on Monday August 14, 2023 @01:26PM (#37123802)
OK got it, thanks for clarifying it