Skip site navigation (1) Skip section navigation (2)

Re: automating CF submissions (was xlog location arithmetic)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: automating CF submissions (was xlog location arithmetic)
Date: 2012-01-17 17:24:05
Message-ID: 20362.1326821045@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 01/16/2012 05:40 PM, Alvaro Herrera wrote:
>> It's expected that we'll get a more reasonable interface to attachments,
>> one that will allow you to download patches separately.  (Currently,
>> attachments that have mime types other than text/plain are already
>> downloadable separately).

> Are you really sure about that? My recent JSON patch is at 
> <http://archives.postgresql.org/message-id/4F12F9E5.3090801@dunslane.net>. 
> I don't see any download link for the patch there, yet my mailer set the 
> attachment type to text/x-patch, not text/plain.

Yeah, AFAICT the archives treat text/x-patch the same as text/plain.
I tend to send stuff that way if I mean it primarily to be read in the
email.  If I'm thinking people will download and apply it, it's better
to gzip the patch and pick a mime type appropriate to that, because that
makes it much easier to pull the patch off the archives at need, at the
cost that you can't just eyeball it in your mail reader.

Anyway, I agree with the general tenor of this thread that it'd be nice
to reduce the impedance mismatches a bit.  Don't have any great ideas
about specific ways to do that.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Marti RaudseppDate: 2012-01-17 17:35:51
Subject: Patch review for logging hooks (CF 2012-01)
Previous:From: Matteo BeccatiDate: 2012-01-17 17:22:12
Subject: Re: automating CF submissions (was xlog location arithmetic)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group