{"thread":{"id":"58809","subject":"git-p4 should memorize the relevant P4* variables during 'git p4 clone' instead of requiring them again for sync/sumbit operations","startedAt":"2022-11-17T08:09:44Z","lastAt":"2022-11-17T08:09:44Z","messageCount":1,"participants":["Yuri"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"467424","messageId":"de2e1474-e044-72d2-1553-5943c7cdcbd4@tsoft.com","threadId":"58809","inReplyTo":null,"subject":"git-p4 should memorize the relevant P4* variables during 'git p4 clone' instead of requiring them again for sync/sumbit operations","fromName":"Yuri","fromEmail":"yuri@rawbw.com","sentAt":"2022-11-17T08:09:36Z","receivedAt":"2022-11-17T08:09:44Z","isPatch":false,"sender":{"key":"yuri@rawbw.com","avatar":null},"body":"Currently 'git p4 submit' requires the variable P4CLIENT to be exactly \nsame as it was during 'git p4 clone'. When people have multiple \nrepositiories it is easy to confuse P4CLIENT and this leads to strange \ncryptic errors and repository becoming unusable.\n\n\nI suggest to improve git-p4: it should memorize the P4CLIENT value \nduring 'git p4 clone' and use the same value when in calls the p4 \nexecutable regardless of what P4CLIENT value is actually set.\n\n'git p4 submit' and 'git p4 sync' should probably also require the \nrepository to have the same path as it had during 'git p4 clone', \nbecause this is what the P4 client is tied to.\n\nThis would make git-p4 a lot less error prone due to mismatching \nP4CLIENT values.\n\nIt is easy for users to confuse P4CLIENT and run 'git p4 xx' from a \nwrong (mismatching) repository, causing errors difficult to recover from.\n\n\nThanks,\n\nYuri\n\n\n"}]}