Re: [HACKERS] Patch Submission Guidelines

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-patches(at)postgresql(dot)org
Subject: Re: [HACKERS] Patch Submission Guidelines
Date: 2006-02-24 17:18:22
Message-ID: 200602241718.k1OHIMS13586@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:
> Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
> > On Thursday 16 February 2006 00:27, Tom Lane wrote:
> >> * avoid unnecessary whitespace changes. They just distract the
> >> reviewer, and your formatting changes will probably not survive
> >> the next pgindent run anyway.
>
> > would diff -c --ignore-space-change be better?
>
> Hmm. Not sure --- there are situations where whitespace *does* matter,
> so having that as a blanket policy doesn't seem wise. Also I'm worried
> that a diff made this way would confuse patch (for instance, because
> line numbers following an omitted whitespace change wouldn't match up).
> Probably best not to go there, but just focus on the point about keeping
> the patch readable.

Agreed. It isn't that we don't want whitespace changes, just that we
don't want insignificant whitespace changes.

--
Bruce Momjian http://candle.pha.pa.us
SRA OSS, Inc. http://www.sraoss.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2006-02-24 17:18:57 Re: fsutil ideas
Previous Message Bruce Momjian 2006-02-24 17:16:58 Re: [HACKERS] Patch Submission Guidelines

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2006-02-24 19:57:19 Re: how solve diff of API counstruct_md_array between
Previous Message Bruce Momjian 2006-02-24 17:16:58 Re: [HACKERS] Patch Submission Guidelines