> This has been true for a number of cases over the years: whether the > "repostiory format", or the wire protocol, sometimes changes which > materially *improve* the user's experience may require upgrading the > client on the user's machine. In the case of SVN, upgrading to 1.5 gets > vastly better merging support; in the case ob bzr, the win is > performance when working against a large tree. The question is whether upgrades on the server force upgrades on the clients. For subversion, this is not the case: Older clients continue to work correctly with 1.5 servers - they just can't use the merge functionality. IIUC, for bzr, this is different: if the repository format is upgraded, older clients will fail to do anything, not even a regular checkout. > AFAICS, no real user (one already using bzr to work with the Python > tree) has objected. Apparently not (assuming David Cournapeau does not actually use bzr) Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4