Removing changesets from the local cache can be useful because the local changeset cache consumes memory, though.
You can remove changesets you don't need from the cache in order to free up the memory.
That is, I was working from this bit of documentation: There are users and organizations.
Organizations have many users and users can belong to many organizations.
Other more advanced features are provided by the Changeset Query Dialog.
Here are a few scenarios that may help you decide whether Gluon is a good fit for you and your team: file allows you to lock files upon checkout which prevents others from modifying those files while you are working on them.
To use Gluon for the first time you will need to create your first workspace by configuring the Plastic SCM server (IP address or Name).
If you need help with this set-up then we recommend that you consult with your sysadmin.
If you want to download the list of open changesets you own JOSM locally maintains a cache of the changesets downloaded from the OSM server.
The content of this cache is displayed in the upper half of the Changeset Manager. Removing a changeset from the cache doesn't affect the OSM server. In fact, it is to delete a changeset on the server.