{"thread":{"id":"62048","subject":"Adding a custom submit tool to git p4","startedAt":"2024-09-03T19:31:04Z","lastAt":"2024-09-03T19:31:04Z","messageCount":1,"participants":["faust1002"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"502057","messageId":"CALHxJxG+xdV4T3ZGMTMiHPzOt_Rm1yh9b=-v0RjJHJn0Z=jiZw@mail.gmail.com","threadId":"62048","inReplyTo":null,"subject":"Adding a custom submit tool to git p4","fromName":"faust1002","fromEmail":"faust1002@gmail.com","sentAt":"2024-09-03T19:30:51Z","receivedAt":"2024-09-03T19:31:04Z","isPatch":false,"sender":{"key":"faust1002@gmail.com","avatar":null},"body":"Hello guys,\nI hope you don't mind so direct approach.\nI work in a company where P4 is used as version control system. As you\ncan probably guess, it is slow, heavy and works in only 50% of cases.\nIn the interest of my mental health, I'd like to use git. But again,\ndirect migration to git is not possible due to the company policy. So\nI thought about using git p4 as a substitute. Of course it is not so\neasy. Clone / rebase / sync work as expected, but there's a problem\nwith submit. My company uses its own utility to submit changes instead\nof the regular p4 utility (again, the company policy). The issue here\nis that git-p4.py has hardcoded \"p4\" as part of p4_build_cmd function\nand there is no way of changing it.\nI can prepare a patch to change it (I know that dedicating some of my\nfree time to something my company will clearly benefit from is a dumb\nidea, but I'm kind of desperate here) but before I do anything I have\ntwo questions\n1) Will such patch be accepted in the first place? This is quite odd\nidea and I wouldn't be surprised if you don't want to agree on it.\n2) If the answer is yes, do you have any recommendation regarding the\npotential implementation?\nKind regards\n"}]}