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
In a recent dicussion on how we might improve the current "hardlink farm" file system transaction model, it became clear that it might be wise to create an API that enables us to experiment with different fstx drivers.
This issue can be closed once the existing "hardlink farm" fstx driver has been ported to this new api.
The API needs to ensure that there is a strategy for taking a selection of assets and putting them into some aggregate that can be presented to the user as a /usr folder.
The text was updated successfully, but these errors were encountered:
In a recent dicussion on how we might improve the current "hardlink farm" file system transaction model, it became clear that it might be wise to create an API that enables us to experiment with different fstx drivers.
This issue can be closed once the existing "hardlink farm" fstx driver has been ported to this new api.
The API needs to ensure that there is a strategy for taking a selection of assets and putting them into some aggregate that can be presented to the user as a /usr folder.
The text was updated successfully, but these errors were encountered: