Comments on merge proposals submitted by e-mail get cut off

Bug #752327 reported by Soren Hansen
This bug report is a duplicate of:  Bug #701525: Merge-proposal reply truncated. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
New
Undecided
Unassigned

Bug Description

On this merge proposal:

   https://code.launchpad.net/~justin-fathomdb/nova/add-xsd/+merge/54418

I submitted the following e-mail:

------------8<-------------8<---------------------
MIME-Version: 1.0
Received: by 10.42.2.137 with HTTP; Tue, 5 Apr 2011 23:52:23 -0700 (PDT)
X-Originating-IP: [95.166.159.124]
In-Reply-To: <email address hidden>
References: <email address hidden>
 <email address hidden>
Date: Wed, 6 Apr 2011 08:52:23 +0200
Delivered-To: <email address hidden>
Message-ID: <email address hidden>
Subject: Re: [Merge] lp:~justin-fathomdb/nova/add-xsd into lp:nova
From: Soren Hansen <email address hidden>
To: <email address hidden>
Cc: justinsb <email address hidden>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

2011/3/31 justinsb <email address hidden>:
> The fact is, we are supposed to be supporting this API.

Right. So this should be referenced from a blueprint or something.

Documentation should document how things *are*, not how we wish they were.

> This is the spec
> for our "v1.0" endpoint. =C2=A0While XML can be fugly, it does have the b=
enefit
> of being an excellent spec for the wire format, which it's easy to test
> against. =C2=A0Most of the specs carry across to our JSON output. =C2=A0I=
f we want our
> API to be compatible with the many existing tools out there that talk to =
the
> CS API, this is the spec we have to validate against.

I completely agree, so if these schemas were used for this validation,
I'd be perfectly happy with it.

> I think the right thing to do is to merge these specs, on the ground that
> they are the best specs we've got for what we're supposed to be targeting=
.

"supposed to be" are the operative words for me here.

If you would stick the files in a directory named
"schemas_that_we_ought_to_be_following_but_are_not",
"wishful_thinking" or even "somebody_elses_schema" that would help
immensely. :)

--=20
Soren Hansen =C2=A0 =C2=A0 =C2=A0 =C2=A0| http://linux2go.dk/
Ubuntu Developer =C2=A0 =C2=A0| http://www.ubuntu.com/
OpenStack Developer | http://www.openstack.org/
------------8<-------------8<---------------------

As you can see on the merge proposal, everything after "> they are the best specs we've got for what we're supposed to be targeting" got cut off.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.