You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My git repository has a symlink pointing into a VOB. From a..b the symlink moved. gitcc checkin failed (after uncoing checked out files) with error: Exception: cleartool: Error: Not an element: "example.hpp". This seems to be due to gitcc only considering the type output of git diff around here and then status.Rename trying to check out the file. Per this article it looks like the typical way to edit a VOB symbolic link is to delete it and recreate it. Any change here will also need to change the conflict check logic since the symlink created with cleartool ln will have a different object hash than the existing symlink in git. or do a symlink-specific check.
In the next commit I had actually changed the symlink into a file, so as a workaround I checked out the directory, replaced the symlinks with files, then checked in and executed gitcc checkin --force.
The text was updated successfully, but these errors were encountered:
My git repository has a symlink pointing into a VOB. From
a..b
the symlink moved.gitcc checkin
failed (afterunco
ing checked out files) with error:Exception: cleartool: Error: Not an element: "example.hpp"
. This seems to be due togitcc
only considering thetype
output ofgit diff
around here and thenstatus.Rename
trying to check out the file. Per this article it looks like the typical way to edit a VOB symbolic link is to delete it and recreate it. Any change here will also need to change the conflict check logic since the symlink created withcleartool ln
will have a different object hash than the existing symlink in git. or do a symlink-specific check.In the next commit I had actually changed the symlink into a file, so as a workaround I checked out the directory, replaced the symlinks with files, then checked in and executed
gitcc checkin --force
.The text was updated successfully, but these errors were encountered: