[MERGE] Make built-in plugins display the same version than bzrlib.

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Vincent Ladeuil wrote:
>>>>>> "vila" == Vincent Ladeuil <v.ladeuil+lp at free.fr> writes:
> 
>>>>>> "jam" == John Arbash Meinel <john at arbash-meinel.com> writes:
>     jam> Vincent Ladeuil wrote:
>     >>> I've seen version [unknown] for built-in plugins far too much in
>     >>> bug reports.
>     >>> 
>     >>> Let's stop that sillyness,
>     >>> 
>     >>> Vincent
>     >>> 
>     >>> 
> 
>     jam> Why not just give builtin plugins an explicit
>     jam> version_info of their own?
> 
> Because they are part of bzrlib and as such we will never use two
> different versions of the plugin for a given bzrlib version[1].
> 
> I'll merge as is but if you can convince me otherwise, I'll send
> another submission.
> 
>    Vincent
> 
> [1]: I have other possible explanations but they don't fit in
> this email margins :-)
> 

Well, it would be reasonable to have them be expressed as the last
version of bzr in which the plugin which was actually modified.
Considering the code is 100% identical, it seems a bit odd to release
the exact same code as 1.12, 1.13, 1.14, etc. Certainly if someone
wanted to know if the plugin actually changed, they wouldn't be able to
use "bzr version $PLUGIN" to figure that out...

I don't really care, just how I would do release numbering of something.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkng75oACgkQJdeBCYSNAAPR5ACg1DxMWFYAkH57BCFwTiMWMnfr
ebcAoLpkYBW5hEFparJXY2WnCLokb2kH
=lrXJ
-----END PGP SIGNATURE-----