Feature Request: 'bzr mv --after' to tell bzr that file(s) have already been moved in the working tree

Aaron Bentley aaron.bentley at utoronto.ca
Fri Nov 3 14:53:23 GMT 2006


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

Hanns-Steffen Eichenberg wrote:
> BTW. i have read the 'HACKING' document (version from 03-11-2006), but i
> still have some questions regarding the process.

You may also find this useful:
http://bazaar-vcs.org/BzrGivingBack

(In fact, if you don't find it useful, please say why, and I'll fix it)

> Can i just post a
> [patch] with the enhancement to the mailing list or should i use the bug
> tracker to open a feature request first?

We prefer that you mail the list with [patch] or [merge].  It means that
everyone gets a chance to discuss the change.

> Since the proposed enhancement is visible to the end user, is there some
> sort of 'board' that decides this functionality besides the mentioned
> voting mechanism?

No.  We try to reach consensus on proposed changes, but ultimately, the
core developers are responsible for putting things in or rejecting them.
 (And as project leader, Martin Pool has a special role.)

> Do i have to become some sort of official commiter first, or are code
> drafts welcome from new people like me?

They're very much welcome.

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

iD8DBQFFS1fi0F+nu1YWqI0RAoP8AJ9VGweUFQgT1VfGMWj1nL3GwUcWYACfcRK6
JWDdiRfm2fbCBLBsDkhTYW0=
=xZRW
-----END PGP SIGNATURE-----




More information about the bazaar mailing list