Re: Git conversion status
От | Robert Haas |
---|---|
Тема | Re: Git conversion status |
Дата | |
Msg-id | AANLkTikkAssjvmBTg+0+2HrTh+9_G4ehTsj1yBwL-RMs@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Git conversion status (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Git conversion status
|
Список | pgsql-hackers |
On Tue, Sep 21, 2010 at 12:31 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Magnus Hagander <magnus@hagander.net> writes: >> On Tue, Sep 21, 2010 at 05:38, Tom Lane <tgl@sss.pgh.pa.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
В списке pgsql-hackers по дате отправления: