Mark Phippard wrote:
> 1) You could upgrade everything to 1.5, be using merge tracking on a
> project for months, and anyone can come along and perform and commit a
> merge using an older client (which will not create the merge tracking
> information). We do not seem to care.
> 2) Similarly, someone can create a branch with an older client and
> not have their mergeinfo generated.
> 3) Users can do --depth checkouts and have a lot more data sent to
> the client then they were expecting. As Stefan pointed out we also
> experience this with log --limit and older servers.
Yes, my boss already complained about that: he tried to checkout the
subclipse code which took way too long. I then suggested he use the
--depth feature and just check out what he really wanted - didn't work
("that thing is broken!") because it took as long as before.
> 4) As you pointed out someone can use a 1.5 client with a 1.4 server
> and get semi merge tracking features and not realize it does not
> completely work.
> There are probably others. I just do not understand why this
> situation is so special. I think numbers 1 and 4 above are far worse.
> Do you have emails queued up for those issues?
I think we need a way for the server (hook script maybe) to reject
clients < 1.5.
I *know* that this will be a very big issue in companies: they want to
prevent users from using older clients and mess up the merge info.
As far as I know, that's currently not possible. But IMHO it must be
possible - our mailing list will get flooded with requests for that feature.
Server admins will be reluctant to upgrade their servers when they know
that the merge tracking info can be messed up with older clients,
because they usually can't control what clients are used. The only way
for them to prevent a mess is to have the ability to reject older
clients directly on the server.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Oct 19 23:11:24 2007