merge proposals do not permit attachments (via the API / model)

[Robert Collins]

This bug is for LP API and readonly display of attachments in merge proposals. Attachments are useful for robots like tarmac and pqm reporting on issues encountered doing merges or other statistics about a merge.

[Robert Collins (lifeless)]

I'm not sure this is a duplicate; I don't care about attaching things via
the web UI - I want to attach them via the API, and I don't want to update
diffs, which that bug seems to be about.

[James Westby (james-w)]

Feel free to unduplicate and reword your bug to be about the API then.

Thanks,

James

[Robert Collins (lifeless)]

Well I'm not sure enough of the code structure to assert that it is or
isn't, so I'll wait for a lp-code dev to comment on it. If one could be
fixed without fixing the other, then I think we should undup it. That may
not be the case though.

[Aaron Bentley (abentley)]

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

On 04/14/2010 07:04 AM, Robert Collins wrote:
> *** This bug is a duplicate of bug 405313 ***
> https://bugs.launchpad.net/bugs/405313
>
> I'm not sure this is a duplicate; I don't care about attaching things via
> the web UI - I want to attach them via the API, and I don't want to update
> diffs, which that bug seems to be about.

Diffs were simply an example. The only difference I see is that you're
talking about the API and bug 405313 is talking about the web.

Aaron

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

iEYEARECAAYFAkvFxp4ACgkQ0F+nu1YWqI218gCdHoUPz0Oh15BPr0Oo/aoW7sE/
vB0AnRYRHV8PozhK54/LhJwd8YafMZrb
=Bhtd
-----END PGP SIGNATURE-----

[Robert Collins (lifeless)]

Thumper said that two bugs made sense, so I've undupped and made this one more specific than it was.