Erik Huizinga <huizinga.erik@xxxxxxxxx> writes: > In other words: how can I, an individual end user, know what I can > safely learn about these commands, and what can not? The restore/switch commands are thought to be the future, and for a better future, we still want to polish them further, which means they may gain new features, their existing behaviour may change, or some features that are found to be bad for users may be dropped. And we will know what new features are desirable, which parts of their existing behaviour should be improved in what way, and which parts of their existing features cause confusion to users and need to be dropped, only by listening to those who actually use them in their daily life. That is what an experiment is. By definition, we won't know what will going to change. Users who want to help improve future Git are encouraged to use these experimental commands and complain (especially when they find that these commands do not work for them in their workflow better than "git checkout", which these commands are meant to replace). Their voices will be heard and the commands may gain what they want and lose what they do not want. Users who do not care about participating in polishing these two commands for a better Git in the future can stick to what they already know, "git checkout". But eventually these users would have to learn "switch/restore" and their then-current set of features, as (hopefully) they would be much better than "git checkout" by then. Thanks.
