Karl Fogel wrote:
> But for license-1.html, it's every source file in our repository, and
> a bunch of other files as well :-). I think the best strategy would
> be to fix up the above three first, in a separate commit, and then do
> a third commit taking care of all the license-1.html instances
> (that'll be a non-trivial amount of work, though, if you don't have
> time I don't think it's urgent).
>
I noticed this weekend that the Windows installer refers to the
license-1.html file like this:
"This is version 1 of this license. It is also available online at
http://subversion.tigris.org/license-1.html. If newer versions of this
license are posted there (the same URL, but with the version number
incremented: .../license-2.html, .../license-3.html, and so on), you may
use a newer version instead, at your option. "
There probably was a reason why the filename included the version, is
that reason gone now? If a new version of the license is released, users
of a previous version of Subversion still have the option to comply to
the old version, not to the new. If I understood correctly, in your
current proposal we will automatically update the license file to the
latest version?
regards,
Lieven.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 18 18:54:14 2006