The whole "oh, no, some hidden stuff that looks like a virus signature exists got put on disk, even though it can't be executed or actually cause any harm" is honestly not Bazaar's problem. If your antivirus tool refuses to let you work (i.e., you can't tell it to ignore the content of Bazaar pack files, which make sense to omit from a virus scan since obviously these files are not executable in the repository itself) then you need to get a better tool.
This is really not related to merge directives anyway since the same situation could occur by merging a remote branch.
Back on topic: as to treating merge directives as branches for "bzr log feature1.patch" or "bzr st -r submit: feature1.patch", etc., I say +100!! I understand it's probably a lot of internal work to get this going for Bazaar, but as a user this would be extremely convenient.
The whole "oh, no, some hidden stuff that looks like a virus signature exists got put on disk, even though it can't be executed or actually cause any harm" is honestly not Bazaar's problem. If your antivirus tool refuses to let you work (i.e., you can't tell it to ignore the content of Bazaar pack files, which make sense to omit from a virus scan since obviously these files are not executable in the repository itself) then you need to get a better tool.
This is really not related to merge directives anyway since the same situation could occur by merging a remote branch.
Back on topic: as to treating merge directives as branches for "bzr log feature1.patch" or "bzr st -r submit: feature1.patch", etc., I say +100!! I understand it's probably a lot of internal work to get this going for Bazaar, but as a user this would be extremely convenient.