search for: interceded

...crutiny. (It's random-number driven so every run is different.) A couple months ago I reported a few simple bugs which this script found and you fixed them; thanks. Then it started finding problems for which it's harder to isolate simple reproducible test cases. Vacations and other work interceded but now Apple is pleased to give you the script itself to allow you to iterate faster. Here are some examples of it running. One time only, pass the --init argument to store some template messages used by the real tests: $ ./catenate.pl --host your.test.server --user testuser --password 1234 --in...

On 2007-06-30, at 18:36, Reid Spencer wrote: > I'm finding the current layout a bit frustrating, not to mention > that it breaks all the documentation. [...] I would rather see it > laid out like this: > > trunk/llvm/... > trunk/stacker/... > trunk/java/... > > branches/llvm/... > branches/stacker/... > branches/java/... > >

Hi Gordon, On Sun, 2007-07-01 at 08:22 -0400, Gordon Henriksen wrote: > On 2007-06-30, at 18:36, Reid Spencer wrote: > > > > I'm finding the current layout a bit frustrating, not to mention > > that it breaks all the documentation. [...] I would rather see it > > laid out like this: > > > > > > > > > trunk/llvm/... > >

All, I'm finding the current layout a bit frustrating, not to mention that it breaks all the documentation. We currently have modules laid out like this: llvm/trunk/... llvm/branches/... llvm/tags/... stacker/trunk/... stacker/branches/... stacker/tags/... and similarly for all the other modules (test-suite, java, poolalloc, etc.). Unfortunately, this "standard"

Hi all, I have a column that peeks its value from a sequence (postgres) some times. Other times, I set it to a certain value. This column has a default value of "nextval(''the_sequence'')"... When I want that this column peeks the value from the sequence, I do this: obj = Mymodel.new obj.some_column1 = blah obj.some_column2 = blah obj.some_column3 = blah obj.save! but