https://bugs.kde.org/show_bug.cgi?id=376789
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=376789
--- Comment #6 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=376789
Justin Zobel changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=376789
--- Comment #4 from Massimo Burcheri ---
I had some old clients from 2007 that did not need P4CONFIG to be set, and the
current from 2017 doesn't either.
afaik the default always was to configure all in the environment:
P4LOC
https://bugs.kde.org/show_bug.cgi?id=376789
--- Comment #3 from Morten Danielsen Volden ---
(In reply to Massimo Burcheri from comment #2)
> Having P4CONFIG unset is a valid P4 environment.
True.
IIRC, older p4 clients needs the P4CONFIG to be set - no?
Also. If you P4
https://bugs.kde.org/show_bug.cgi?id=376789
--- Comment #2 from Massimo Burcheri ---
Having P4CONFIG unset is a valid P4 environment. But the perforce plugin
refuses to load.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376789
--- Comment #1 from Morten Danielsen Volden ---
P4CONFIG only points to the filename that the plugin should search a given
directory structure for.
So if you have a project folder structure like this:
MyCoolProject
Foo
https://bugs.kde.org/show_bug.cgi?id=376789
Kevin Funk changed:
What|Removed |Added
CC||mvold...@gmail.com
--
You are