Re: pgsql: Correct tense in log message

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Correct tense in log message
Date: 2013-03-18 20:08:00
Message-ID: 20130318200800.GF16641@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Sat, Mar 16, 2013 at 04:31:21PM -0400, Peter Eisentraut wrote:
> On Fri, 2013-03-08 at 14:16 -0500, Bruce Momjian wrote:
> > On Sun, Feb 24, 2013 at 04:53:18AM +0000, Peter Eisentraut wrote:
> > > Correct tense in log message
> > >
> > > Branch
> > > ------
> > > REL9_0_STABLE
> > >
> > > Details
> > > -------
> > > http://git.postgresql.org/pg/commitdiff/a8d80461a201051b67c286e1a83d00844d7cc6d8
> > >
> > > Modified Files
> > > --------------
> > > src/backend/commands/vacuumlazy.c | 2 +-
> > > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > Uh, do we really want to be churning translated messages in backbranches
> > for this?
>
> Not normally, but this was just added in the previous point release, and
> so it seemed easier to just "correct" it before it lives too long.

Oh, I was not aware of that.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Simon Riggs 2013-03-18 22:39:09 pgsql: Add reliability docs about storage/memory corruptions.
Previous Message Tom Lane 2013-03-18 17:35:06 pgsql: Improve documentation of EXTRACT(WEEK).