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

Re: pgsql: And another one

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Michael Meskes <meskes(at)postgresql(dot)org>
Cc: pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: And another one
Date: 2010-01-05 17:20:07
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committers
This kind of commit message is pretty much useless. If you want to do
a git blame/cvs annotate/whatever later, it gives exactly zero

Isn't it better to just reuse the previous commit message? That will
also allow tools to group the commits together (if you're lucky, they
might even show up in git as a single commit)

(if you actually need this many different commits, of course :P)


On Tue, Jan 5, 2010 at 18:10, Michael Meskes <meskes(at)postgresql(dot)org> wrote:
> Log Message:
> -----------
> And another one
> Modified Files:
> --------------
>    pgsql/src/interfaces/ecpg/include:
>        pgtypes_numeric.h (r1.16 -> r1.17)
>        (
>    pgsql/src/interfaces/ecpg/test/expected:
>        compat_informix-sqlda.c (r1.7 -> r1.8)
>        (
>        sql-sqlda.c (r1.7 -> r1.8)
>        (
> --
> Sent via pgsql-committers mailing list (pgsql-committers(at)postgresql(dot)org)
> To make changes to your subscription:

 Magnus Hagander

In response to


pgsql-committers by date

Next:From: Stefan KaltenbrunnerDate: 2010-01-05 17:24:39
Subject: Re: [COMMITTERS] pgsql: Get rid of the need for manual maintenance of the initial
Previous:From: Michael MeskesDate: 2010-01-05 17:10:23
Subject: pgsql: And another one

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