Re: [HACKERS] 6.6 items
От | Bruce Momjian |
---|---|
Тема | Re: [HACKERS] 6.6 items |
Дата | |
Msg-id | 199906090203.WAA27054@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: [HACKERS] 6.6 items (Thomas Lockhart <lockhart@alumni.caltech.edu>) |
Список | pgsql-hackers |
> > > > Or you talk that this should be mentioned in > > > > announcement/release notes? > > > I've added a mention of this in the release notes, and (Bruce) since > > > I'll be regenerating INSTALL and HISTORY it will be included in those. > > > I *should* be able to retrofit it into admin.ps.gz also... > > Added to release notes: > > Good idea to add this. I also added to the Enhancements list: > > pg_dump now can generate consistent snapshots on active databases(Vadim) > > ?? "I've added a mention of this in the release notes" was supposed to > keep you from doing anything! Wholesale reorganization isn't likely to > make it into hardcopy, and I'm not happy about that. Please remember > that I've already generated hardcopy for a release that was supposed > to happen tomorrow, so gratuitous changes aren't going to go over very > well with me :/ > > I see that lock.sgml has been updated. But I'll probably need ~2 days > elapsed to finish off the docs, as I mentioned last week. OK, I am confused. What should we do or not do? I thought release notes->HISTORY was OK for changes. I realize lock.sgml is harder. Is it because the release notes are also in admin.gz? -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026
В списке pgsql-hackers по дате отправления: