Skip site navigation (1) Skip section navigation (2)

Re: psql possible TODO

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Richard Troy <rtroy(at)ScienceTools(dot)com>, Stephen Harris <lists(at)spuddy(dot)org>, "Jim C(dot) Nasby" <jim(at)nasby(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: psql possible TODO
Date: 2007-01-29 21:56:00
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Alvaro Herrera wrote:
> > I will claim this for now. I will let it go if I can't get at least
> > something productive done on it by end of January.
> Now that the embargo period seems to be over, I think it would be a good
> time to add it to the TODO list.  Also, I'd modify the idea slightly to
> allow a more general facility, using %-escapes (or similar) for line
> numbers, dates and so on.  Bash allows something like this (albeit
> limited to only times) using the HISTTIMEFORMAT environment variable.
> This is the first case I know of of an embargo to an agreed TODO item.
> Why was it put in place?  I find it distracting, because the item has to
> be put on someone else's TODO list and then that person has to pinch
> others to get it added to the central TODO list.  Not sure I see the
> point.  (I understand about bashing Joshua ---a sport I also practice in
> Command Prompt's internal lists ;-) --- but in this case it seems to be
> counterproductive).

The only reason it isn't on the TODO is because I am still catching up
for the 8.3 queue.  I know of no embargo.

  Bruce Momjian   bruce(at)momjian(dot)us

  + If your life is a hard drive, Christ can be your backup. +

In response to

pgsql-hackers by date

Next:From: Nikolay SamokhvalovDate: 2007-01-29 22:12:20
Subject: Re: XML type and XPath
Previous:From: Bruce MomjianDate: 2007-01-29 21:54:41
Subject: Re: psql possible TODO

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group