On 29.5.2007, at 9.01, Shane Vitarana wrote:
Well there appears to be at least 3 CI reports going on here. The
CC.rb one is prefixed with [CruiseControl] and then there are ones by
[EMAIL PROTECTED] and [EMAIL PROTECTED] Are these necessary
or did I miss something amidst the traffic?
Yes.
"bitsweat" has given AR/SQLServer some love, but it's still unhappy...
http://dev.rubyonrails.org/changeset/6888
r6888 | bitsweat | 2007-05-28 23:40:33 -0700 (Mon, 28 May 2007) | 1 line
Routing: drop semicolon and comma as
"bitsweat" has given AR/Oracle some love, but it's still unhappy...
http://dev.rubyonrails.org/changeset/6888
r6888 | bitsweat | 2007-05-28 23:40:33 -0700 (Mon, 28 May 2007) | 1 line
Routing: drop semicolon and comma as rou
The build failed.
See http://cruisecontrolrb.thoughtworks.com/builds/RubyOnRails/6888 for details.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rub
Well there appears to be at least 3 CI reports going on here. The
CC.rb one is prefixed with [CruiseControl] and then there are ones by
[EMAIL PROTECTED] and [EMAIL PROTECTED] Are these necessary
or did I miss something amidst the traffic?
Shane
On 5/29/07, Kevin Clark <[EMAIL PROTECTED]> wrot
I love the fact that all of the continuous integration reports go to
the core list. It means we have to pay attention. At the same time, it
sort of floods the rest of my core threads. Could we prefix CI reports
with [CI] or [CONTINT] or something similar so I can write a filter?
--
Kevin Clark
h
"bitsweat" has kicked AR/Oracle while it was down...
http://dev.rubyonrails.org/changeset/6887
r6887 | bitsweat | 2007-05-28 19:42:31 -0700 (Mon, 28 May 2007) | 1 line
Correct flash discard rdoc. Closes #8502 [kampers]
"bitsweat" has kicked AR/SQLServer while it was down...
http://dev.rubyonrails.org/changeset/6887
r6887 | bitsweat | 2007-05-28 19:42:31 -0700 (Mon, 28 May 2007) | 1 line
Correct flash discard rdoc. Closes #8502 [kampers]
-
"bitsweat" has kicked AR/SQLServer while it was down...
http://dev.rubyonrails.org/changeset/6886
r6886 | bitsweat | 2007-05-28 19:40:34 -0700 (Mon, 28 May 2007) | 1 line
Inflections: MatrixTest -> MatrixTests instead of Ma
"bitsweat" has given AR/Oracle some love, but it's still unhappy...
http://dev.rubyonrails.org/changeset/6886
r6886 | bitsweat | 2007-05-28 19:40:34 -0700 (Mon, 28 May 2007) | 1 line
Inflections: MatrixTest -> MatrixTests i
The build failed.
See http://cruisecontrolrb.thoughtworks.com/builds/RubyOnRails/6887 for details.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rub
The build failed.
See http://cruisecontrolrb.thoughtworks.com/builds/RubyOnRails/6886 for details.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rub
"bitsweat" has given AR/SQLServer some love, but it's still unhappy...
http://dev.rubyonrails.org/changeset/6885
r6885 | bitsweat | 2007-05-28 19:13:53 -0700 (Mon, 28 May 2007) | 1 line
Update CHANGELOG attribution.
---
The build failed.
See http://cruisecontrolrb.thoughtworks.com/builds/RubyOnRails/6885 for details.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rub
"bitsweat" has given AR/Oracle some love, but it's still unhappy...
http://dev.rubyonrails.org/changeset/6884
r6884 | bitsweat | 2007-05-28 19:07:08 -0700 (Mon, 28 May 2007) | 1 line
Wordsmith generator USAGEs.
The build failed.
See http://cruisecontrolrb.thoughtworks.com/builds/RubyOnRails/6884 for details.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rub
Yes.. but changeset 6883 wasn't meant to address this failure and it
happened before this changeset.
Shane
On 5/28/07, Michael Schoen <[EMAIL PROTECTED]> wrote:
>
> "bitsweat" has kicked AR/Oracle while it was down...
>
> http://dev.rubyonrails.org/changeset/6883
> --
> > Please take this discussion from -core to -talk.
>
> One last post - sorry Jeremy, couldn't resist:
> http://pastie.caboo.se/65456
>
> Run the script inside the framework root! It finds for loops in Rails code
> and finds out who commited them :)
>
> Here are the results for trunk: {"bitsweat"
On 5/29/07, Jeremy Kemper <[EMAIL PROTECTED]> wrote:
>
>
> Please take this discussion from -core to -talk.
One last post - sorry Jeremy, couldn't resist:
http://pastie.caboo.se/65456
Run the script inside the framework root! It finds for loops in Rails code
and finds out who commited them :)
H
"bitsweat" has kicked AR/Oracle while it was down...
http://dev.rubyonrails.org/changeset/6883
r6883 | bitsweat | 2007-05-28 17:11:56 -0700 (Mon, 28 May 2007) | 1 line
Generated migrations include timestamps by default. Clo
The build failed.
See http://cruisecontrolrb.thoughtworks.com/builds/RubyOnRails/6883 for details.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rub
Please take this discussion from -core to -talk.
Thanks!
jeremy
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rubyonrails-core@googlegroups.com
To
"bitsweat" has given AR/SQLServer some love, but it's still unhappy...
http://dev.rubyonrails.org/changeset/6882
r6882 | bitsweat | 2007-05-28 16:33:54 -0700 (Mon, 28 May 2007) | 1 line
Multibyte strings respond_to the Stri
"bitsweat" has given AR/Oracle some love, but it's still unhappy...
http://dev.rubyonrails.org/changeset/6882
r6882 | bitsweat | 2007-05-28 16:33:54 -0700 (Mon, 28 May 2007) | 1 line
Multibyte strings respond_to the String
The build failed.
See http://cruisecontrolrb.thoughtworks.com/builds/RubyOnRails/6882 for details.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rub
"bitsweat" has kicked AR/SQLServer while it was down...
http://dev.rubyonrails.org/changeset/6881
r6881 | bitsweat | 2007-05-28 15:55:14 -0700 (Mon, 28 May 2007) | 1 line
Generate rdoc with utf-8 charset. Closes #7188 [manf
The build failed.
See http://cruisecontrolrb.thoughtworks.com/builds/RubyOnRails/6881 for details.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rub
On 5/29/07, Giles Bowkett <[EMAIL PROTECTED]> wrote:
>
>
> True; but encouraging programmers new to Ruby to write their code as
> if it were PHP isn't going to result in beautiful code. The risk
> you're taking there is of a glut, in a few years' time, of ugly Rails
> code based on PHP programmers
> > Is scaffolding continuing as normal?
> >
> > When I see posts about getting rid of dynamic scaffolding, does that
> > refer to scaffolding .erb templates, or to the scaffold controller
> > method?
>
> The current plan (as far as I'm aware) is to keep generated
> scaffolding, but replace the ol
> > Total subtle psychological difference, but with Rails having such
> > incredible success, a little thing like that will encourage a lot of
> > new Ruby programmers to use iterators instead of explicit iteration.
> > For many programmers this is a big change:
> >
> > http://technotales.wordpres
The build failed.
See http://cruisecontrolrb.thoughtworks.com/builds/RubyOnRails/6879 for details.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rub
On 5/28/07, Josh Susser <[EMAIL PROTECTED]> wrote:
>
>
> Personally, I never use the for style enumerators, but I don't use
> scaffolding for anything except throwaway code either. YMMV.
That's too bad. Dynamic scaffolding was "throwaway" (temporary) and, because
of that, it's dead now. Resource
On May 27, 2007, at 6:46 PM, giles bowkett wrote:
>
> Hi, I have a change I want to submit, just want to check that it's
> relevant first.
>
> Is scaffolding continuing as normal?
>
> When I see posts about getting rid of dynamic scaffolding, does that
> refer to scaffolding .erb templates, or t
Jochen,
You might get better response by posting to the general Rails mailing
list (http://groups.google.com/group/rubyonrails-talk). This list is
for topics regarding the development of Rails itself.
You probably get the error page because you use save! (with
exclamation mark) instead of
On 28.5.2007, at 4.46, giles bowkett wrote:
Hi, I have a change I want to submit, just want to check that it's
relevant first.
Is scaffolding continuing as normal?
When I see posts about getting rid of dynamic scaffolding, does that
refer to scaffolding .erb templates, or to the scaffold con
I have the following:
class Dummy < ActiveRecord::Base
validates_uniqueness_of :dummy
end
def update
@d = Dummy.new(params[:dummy])
end
<% form_for :dummy, @dummy, :url => {:action => "update" } do |form| %>
<%= error_messages_for :dummy %>
<%= form.text_field :dummy %>
<%= form.t
On 5/28/07, giles bowkett <[EMAIL PROTECTED]> wrote:
>
>
> The scaffolding templates all use
>
> <% for x in y %>
>
> instead of
>
> <% x.each do |y| %>
So? That's the same loop. "for .. in" is easier to write and looks nicer in
templates.
--~--~-~--~~~---~--~~
Yo
37 matches
Mail list logo
