From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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:51:04 |
Message-ID: | AANLkTim7NjkK_a65npsJgPo03aSbS1qBe5G=3vETPGOX@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Sep 21, 2010 at 18:47, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Tue, Sep 21, 2010 at 12:31 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> 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.
>
> 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. I definitely don't
want to group the commits together, and then suddenly tags and commits
are handled differently...
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-09-21 16:55:37 | Re: Git conversion status |
Previous Message | Tom Lane | 2010-09-21 16:47:42 | Re: Git conversion status |