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
The issue is that mepo init uses absolute paths during its setup. So if you move things like this, even the GEOSgcm-OLD clone will point to the new clone because one exists at that part of the tree.
The text was updated successfully, but these errors were encountered:
Just to add that this "renaming" of directories has been common practice among most, if not all, users of the DAS. I will have to ask that we come up w/ a fix for this before releasing the DAS to anyone beyond the small group of individuals presently testing the Git vs CVS migration.
This was discovered by @rtodling. To wit:
/path/to/GEOSgcm
/path/to/GEOSgcm-OLD
/path/to/GEOSgcm
The issue is that
mepo init
uses absolute paths during its setup. So if you move things like this, even theGEOSgcm-OLD
clone will point to the new clone because one exists at that part of the tree.The text was updated successfully, but these errors were encountered: