[PING][MERGE] help topics

[Aaron Bentley]

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

John Arbash Meinel wrote:
> Aaron Bentley wrote:
>>Wouldn't it make sense to use a Registry for this?
> 
> 
> It would, but this specific branch pre-dates Registry. I'd rather see it
> merged and cleaned up, as it has already been in the wild for ~2 months now.

>>There seem to be a lot of unrelated changes here.  These sorts of
>>changes are hostile to branches, and I have a lot of outstanding branches.
> 
> 
> What outstanding branches do you have?

tree-compare, kid-docs, nested-by-value, nested-by-reference,
testframework, checkparents, typechange, autoconflicts

> First, we should try and keep things being integrated often, so
> we don't have large merge issues. Plus, it means bzr core is constantly
> improving. Second, I'd really like to see changes like this happen.
> There are a few code cleanup issues that I would like to see done, but
> as long as we avoid them because we don't want them to cause merge
> conflicts, then the code never gets cleaned up.

Frankly, I think those are a lot less important than playing nice with
people who are trying to make functional improvments to bzr.

> Well, we still use the doc string for Commands, so I don't see us moving
> away from that right away.

Yes, but this is introducing a new API that works that way.  Right now,
changing it is easy.  As soon as the API goes in, changing it is hard.
So I'd like to get it right now.

It shouldn't be hard to change it.  Just use Foo.help instead of
Foo.__doc__.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFFUPcj0F+nu1YWqI0RAkn4AJ9TU9n2ml4X4ZR0e8y7YtU5PndnPgCeM7nS
EtIKCJTrS6zLqV8C5YBY6pg=
=kVBi
-----END PGP SIGNATURE-----