makerakeworkwell version 1.0.2 has been released! * home: <https://github.com/seattlerb/makerakeworkwell> * rdoc: <http://docs.seattlerb.org/makerakeworkwell> make/rake/work/well provides two simple modifications to rake that make working with file tasks cleaner, easier, and faster. Changes: ### 1.0.2 / 2013-02-16 * 1 minor enhancement: * Now compatible with rake 0.9.x up to 10.0.x * 1 bug fix: * Fixed timestamp bug caused by rake 10.x changes to Task#timestamp.
on 2013-02-16 23:36
on 2013-02-18 15:09
Ryan Davis wrote in post #1097280: > makerakeworkwell version 1.0.2 has been released! > > * home: <https://github.com/seattlerb/makerakeworkwell> > * rdoc: <http://docs.seattlerb.org/makerakeworkwell> Wrong urls ? _md
on 2013-02-19 12:14
On Feb 18, 2013, at 06:10 , Michel Demazure <lists@ruby-forum.com> wrote: > Ryan Davis wrote in post #1097280: >> makerakeworkwell version 1.0.2 has been released! >> >> * home: <https://github.com/seattlerb/makerakeworkwell> >> * rdoc: <http://docs.seattlerb.org/makerakeworkwell> > > Wrong urls ? Both work and look right to me.
on 2013-02-20 16:35
Ryan Davis wrote in post #1097748: > On Feb 18, 2013, at 06:10 , Michel Demazure <lists@ruby-forum.com> > wrote: > >> Ryan Davis wrote in post #1097280: >>> makerakeworkwell version 1.0.2 has been released! >>> >>> * home: <https://github.com/seattlerb/makerakeworkwell> >>> * rdoc: <http://docs.seattlerb.org/makerakeworkwell> >> >> Wrong urls ? > > Both work and look right to me. @Ryan : I found the reason. In your post, the closing > is part of the link. Hence clicking on the link raises a 404. _md
on 2013-02-20 16:47
The original email is plaintext only, so the bug is in your email
client.
(RFC 3986 actually has an appendix which outright recommends using < and
>
to delimit URIs. Hence my labelling it a "bug".)
on 2013-02-20 20:31
On Feb 20, 2013, at 07:35 , Michel Demazure <lists@ruby-forum.com> wrote: >>> Wrong urls ? >> >> Both work and look right to me. > > @Ryan : I found the reason. In your post, the closing > is part of the > link. Hence clicking on the link raises a 404. > _md Ah! Good catch by Adam... Yeah. It's your mail client. That's why it works for me. What client are you using btw?
on 2013-02-21 09:55
Ryan Davis wrote in post #1098040: > On Feb 20, 2013, at 07:35 , Michel Demazure <lists@ruby-forum.com> > wrote: > >>>> Wrong urls ? >>> >>> Both work and look right to me. >> >> @Ryan : I found the reason. In your post, the closing > is part of the >> link. Hence clicking on the link raises a 404. >> _md > > Ah! Good catch by Adam... Yeah. It's your mail client. That's why it > works for me. What client are you using btw? Not email : I follow the forum in Firefox 18.0.2 (Windows 7). _md
Please log in before posting. Registration is free and takes only a minute.
Existing account
(Switch to SSL-encrypted connection)
NEW: Do you have a Google/GoogleMail or Yahoo account? No registration required!
Log in with Google account | Log in with Yahoo account
Log in with Google account | Log in with Yahoo account
No account? Register here.