I'm just an observer here, but I thought I'd present an idea. Feel free to
tell me I'm nuts if you don't like it.
It seems to me that there are two main concerns in this area on discussion:
1. How to create a list of patches/review items/etc without adding a
significant amount of noise to this li
On 5/15/07, Tatsuo Ishii <[EMAIL PROTECTED]> wrote:
> Stefan Kaltenbrunner wrote:
> >> They are not stable. The items should point to the archives, which
are
> >> supposedly more stable. (I had already fixed one item in PatchStatus
> >> this morning). Really it would be much nicer to have lin
On 5/5/07, Tom Lane <[EMAIL PROTECTED]> wrote:
"Nathan Buchanan" <[EMAIL PROTECTED]> writes:
> I had the idea of taking the Fourier transform of the waveform and
storing
> the waveform internally that way to reduce storage requirements.
Aside from what Steve sa
Hello!
I have a potential situation where I will have a lot of sensor data coming
in very often. (every second or so) The sensor data is from physics type
measurements, and will normally follow a slowly changing pattern with
sinusoidal disturbances. The overall shape of the data is more important
On 7/16/06, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
Kris Jurka wrote:>>> On Sun, 16 Jul 2006, Tom Lane wrote:>>> [windows buildfarm machines run irregularly]>> For my part the difficulty is scheduling. As a primarily unix user I
> understand cron, but have no idea what the windows equivalent is
A list of simpler TODOs would be great. I might be interested in doing
something (probably w/o the summer of code because I have a summer
job). We'll see after exams finish.
Please post something about where we can find this TODO list when it is available.
Thanks,
NathanOn 4/5/06, Jim Nasby <[EMA
Hi Joshua,
I think the RSS feed is a great Idea! (I personally use InfoRss with
Mozilla) Though it would be nice to reduce the amount of text before
the description (I barely get by the revision number to see the
description) maybe formatted "CMP:R##: Description..." Though
I have no idea ho
