Re: Git conversion status

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Git conversion status
Date: 2010-09-21 16:38:00
Message-ID: AANLkTikkAssjvmBTg+0+2HrTh+9_G4ehTsj1yBwL-RMs@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 21, 2010 at 12:31 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> On Tue, Sep 21, 2010 at 05:38, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> For the archives' sake, below are the missing historical tags that
>>> match available tarballs, plus re-instantiation of the Release_2_0
>>> and Release_2_0_0 tags on non-manufactured commits.  I will push
>>> these up to the repo once it's open for pushing.
>
>> Go for it.
>
> Done.  The commit hook seems to be a bit verbose about that sort of
> thing ... is it worth trying to collapse the pgsql-committers messages
> into one email?

I was thinking the same thing, until I realized that pushing a whole
boatload of tags at the same time is probably going to be an extremely
rare event.

And I am STRONGLY of the opinion that we do NOT want to collapse
multiple *commits* into a single email, at least not unless we start
merging or something. The scripts EDB uses internally do this and it
is, at least IMO, just awful.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-09-21 16:45:20 Re: Git conversion status
Previous Message Tom Lane 2010-09-21 16:31:13 Re: Git conversion status