Comment 28 for bug 250820

On Sun, 2008-08-17 at 15:12 +0000, Matt Zimmerman wrote:
> On Sun, Aug 17, 2008 at 02:32:48PM -0000, Dennis Kaarsemaker wrote:
> > The debian changelog format does not specify any additional fields
> > besides a structured list of changes. The debian .changes format does
> > and is also an rfc2822-like format. The example is a mix of both,
> > starting with a debian changelog and appending some extra rfc2822-like
> > fields.
>
> The purpose of this suggestion was to replace an email format which is hard
> for humans to read (.changes files) with one which is easy for humans to
> read (changelog entries), since emails are primarily for humans to read.
>
> There should be more convenient ways of accessing this data programmatically
> (perhaps launchpadlib?), but if not, perhaps it would be easiest if
> Launchpad simply attached a copy of the .changes file to the message.
This is a very good idea! I will revise the notification email sending
logic accordingly.

> Then, scripts could continue to parse that, while humans could ignore it and
> read the content.
This is the best of both worlds.

Best regards

--
Muharem Hrnjadovic <email address hidden>
Canonical Ltd.

Public key id : 607FAC52
Key fingerprint : 131E FA03 4525 0A6E 7029 29AD B717 2D69 607F AC52