On Tue, Feb 10, 2009 at 08:11:46PM +0100, Magnus Holm wrote:
> Hm... I've always thought 1.5 == 1.5.180... Well, only _why has access to
> the project, so there's not so much we can do :-(
I'm sorry everyone, let's get this all worked out, okay?
Magnus, I'v
rdoc and write howtos for camping with
fastcgi, passenger, and other web servers. I don't know, what do
most people deploy camping on?
_why
___
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
g 2.0 will inspire some breakages.
Augusttime would be better for me, but let's talk about what you
guys want to do.
_why
___
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
oing. Hopefully
today or tomorrow, though!
_why
___
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
d
class ViewYMD # automatically '/view/(\d+)/(\d+)/(\d+)'
def get time; end
end
end
_why
___
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
saves your changes ...
$ git push
# ... sends your changes to github ...
And then, you can just send me a pull request. Go to your camping
page: http://github.com/Bluebie/camping/tree/master. Click on "pull
request" and explain the change.
You're going to love it.
_why
___
Okay, I decided to go with Magnus' :halt idea. I was skeptical, but
good points from the blueberry australian. Anyway, it was only like
a thirteen-byte patch. Now THAT'S a camping patch!
_why
___
Camping-list mailing list
Camping-list@rub
trying to revive the
Junebug wiki <http://github.com/why/junebug> since it's still my
favorite one.
Oh and Passenger is working with Camping 2.0. You just use
`run Blog` in your config.ru (following everything else in the
latest Passenger docs.) Best to wait until
es, then the sessions merely expire.
I guess that's good enough with the warnings there, too.
_why
___
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
ese changes back to the more
relaxed technique.
_why
___
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
tricks into the code that push Ruby's parser and make
everyone look twice. Not all code needs to be a factory, some of
it can just be origami.
_why
___
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
would contain just the hash and the user name.
So, spoof the user name and you're in, you know?
_why
___
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
On Sun, May 25, 2008 at 12:25:08AM +0200, Magnus Holm wrote:
> I've just sent a pull-request to _why with my changes[1] and here is some
> things that I think needs to be done before a (possible) release:
It's been merged, great work, Magnus. I'm not quite to the point of
a
On Fri, May 23, 2008 at 12:16:15PM +0200, Magnus Holm wrote:
> Do you think we should add a protection inside Camping too?
No, if Rack comes with Rack::Lint and Camping now depends on Rack,
then it'd be redundant to have it in Camping as well, you kno
ng "In Less then
> 4K", period.
Instead of saying the obfuscation "just makes development/releasing harder,"
try saying obfuscation "just makes flippancy/esotericism easier."
_why
___
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
).
Splendid! If we can say Camping, the 3K Microframework, then I
think we will really have a reason to bump the big number. I'll wait
for a reaction from zimbatm, but I am euphoric about these changes.
_why
___
Camping-list mailing list
Camping-list@r
In the better interest of helping all of you feel more welcome to
contribute.
http://github.com/why/camping
I will probably close Trac and move to ditz for bug management, if
zimbatm doesn't mind at all. You can look at Shoes' bugs/ directory
for a sneak peek at how that all turns
17 matches
Mail list logo
