[MERGE] Disable the ability to click on tags that are not available in the current view.
aaron at aaronbentley.com
Sun Jul 27 20:00:20 BST 2008
-----BEGIN PGP SIGNED MESSAGE-----
Jelmer Vernooij wrote:
> Am Montag, den 28.07.2008, 06:40 +1200 schrieb Aaron Bentley:
>> Alexander Belchenko wrote:
>>> I guess bzr-gtk has its own mailing list.
>>> Mr. BB! Please send this mails to bzr-gtk ML!
>> BB sends the message to the mailing list for whatever project the patch
>> is determined to be part of. I think this is the correct approach.
> I realize this would probably be more complicated and
> performance-intensive than the current approach, but would it be
> possible to look at the history of the project branch and the merge
> directive and use that to determine the project a merge directive is
> intended for?
It would be possible, but I don't think it's a good idea. If the target
branch is wrong, then the patch is potentially un-mergeable, on the
Bazaar level. So having a BB policy that requires target branches to be
correct is reasonable.
In terms of Bundle Buggy, Bundle Buggy's copy of trunk is not
necessarily up to date. It needs to be able to fetch any missing
revisions from the target branch. If the target branch is wrong, it is
> That would also make it possible to reject merge
> directives for projects that aren't hosted on BB automatically.
I could also do that by rejecting merge directives whose target branches
aren't set to a location that Bundle Buggy recognizes, which is orders
of magnitude simpler.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the bazaar