git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Adding a custom submit tool to git p4

From
Ffaust1002 <faust1002@gmail.com>
Date
Sep 3, 2024, 19:30 UTC
Message-ID
<CALHxJxG+xdV4T3ZGMTMiHPzOt_Rm1yh9b=-v0RjJHJn0Z=jiZw@mail.gmail.com>
Hello guys,
I hope you don't mind so direct approach.
I work in a company where P4 is used as version control system. As you
can probably guess, it is slow, heavy and works in only 50% of cases.
In the interest of my mental health, I'd like to use git. But again,
direct migration to git is not possible due to the company policy. So
I thought about using git p4 as a substitute. Of course it is not so
easy. Clone / rebase / sync work as expected, but there's a problem
with submit. My company uses its own utility to submit changes instead
of the regular p4 utility (again, the company policy). The issue here
is that git-p4.py has hardcoded "p4" as part of p4_build_cmd function
and there is no way of changing it.
I can prepare a patch to change it (I know that dedicating some of my
free time to something my company will clearly benefit from is a dumb
idea, but I'm kind of desperate here) but before I do anything I have
two questions
1) Will such patch be accepted in the first place? This is quite odd
idea and I wouldn't be surprised if you don't want to agree on it.
2) If the answer is yes, do you have any recommendation regarding the
potential implementation?
Kind regards
Message 1 of 1 in “Adding a custom submit tool to git p4”
  1. faust1002Sep 3, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.