[MERGE][BUG] 51980: bzr log <file>returns inappropriate revisions
Kent Gibson
warthog618 at gmail.com
Sat Mar 17 03:16:10 GMT 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Aaron Bentley wrote:
> Aaron Bentley wrote:
>> Aaron Bentley has voted -0. Status is now: Waiting Comment: This
>> doesn't look right, because it only shows revisions that
> introduced
>> the change. It will omit revision_history revisions that merged
>> a change. Since most log views only show revision_history
> revisions, the
>> change will not be shown at all for them. So this would change
>> the current output in ways I don't want.
>
> By the way, here's the regex Bundle Buggy uses to find bug ids:
>
> '(#|bug|bugfix) ?([0-9]+)'
>
> So #51980 would have worked, or BUG 51980, etc.
>
> Aaron
Sorry about the subject, I usually do use the [BUG 51980] form.
I must've been infected by vila's recent patch that used this form.
Can BB handle multiple bugs? e.g. this patch also covers 69477.
And how would I declare that - just add another bug element , e.g.
[BUG 51890][BUG 69477]?
Or would you prefer something like [BUG #51980, #69477]?
Cheers,
Kent.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF+116goxTFTi1P8QRAmJ5AJ9T48ND4qPSlWA7v5YXv+Jkz5dlWwCfftCH
IA0dfF0JMbQe2dJlh+7mETY=
=CaMs
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list