-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue #122: support perforce - first part #123
base: master
Are you sure you want to change the base?
Conversation
The travis error message is strange, it doesn't look like it is caused by my changes. It fails much earlier. |
|
||
Added properties: | ||
|
||
``time`` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have a standard field for this? This way it will not be possible to use my_changest.time regardless of my_changest's type (P4Changeset vs GitChangest vs HgChangeset)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We implemented date
as a base for all 3 vcs-es.
Any update on this pull request? Is there anything I can help with? I don't want to be out of sync with you guys for long time so our branches don't diverge too much. |
…t/perforce/bin, where it is installed by yum
…x with helix-cli rpm. It creates the symlink in post-install script
parsing of p4 command and get_changesets partially works. Tests work. I run them this way:
PYTHONPATH=. python vcs/tests/test_p4.py