Re: Git conversion status

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

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Tue, Sep 21, 2010 at 18:47, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> True. We will be creating four or five tags at a time during
>> back-branch update cycles, but those might well arrive in separate
>> pushes anyway, depending on how Marc chooses to arrange his workflow.

> I could look into if it's possible to group the tags together if they
> come in a single push. I'm not entirely sure it's possible (I don't
> know if the commitmsg script gets called once in total or once for
> each), but I could look into it.

> However, I agree with Robert I doubt it's worth it.

Agreed. It's definitely not something to spend time on before the
update workflow becomes clear --- the case may never arise anyway.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2010-09-21 16:57:27 Re: Serializable snapshot isolation error logging
Previous Message Magnus Hagander 2010-09-21 16:51:04 Re: Git conversion status