Sorry if this is not the place for this.
I'm looking for any reference to potential problems when updating a git client (say from 1.7.N to 1.8.N) with old workspaces.
The scenario is this:
Lots of developers use a single machine for work
They have lots of workspaces created using the old client
We want to upgrade to the new client
Are there any potential problems just upgrading the client and NOT re-cloning their workspaces (or stashing or committing or pushing)?
Subversion had/has some feature that could tell that the workspace was created using an older client and you could magically run something to update the workspace.
I'm not above telling all my developers to commit/push to a feature branch, remove the workspaces and re-clone as needed on a flag-day, but I'd like to know if I have to.
If there is any documentation that talks about this (I know 1.7 is old).
Thanks,
Don Desjardin