This project is archived and is in readonly mode.
Better code formatting and proper fisting of stack trace
Reported by Neeraj Singh | May 14th, 2010 @ 08:09 PM
Some code formatting and proper fisting of stack trace based on this commit. http://github.com/rails/rails/commit/0c37bf8f915cad47e8711f525c220c...
Comments and changes to this ticket
-
Repository May 14th, 2010 @ 08:24 PM
- State changed from new to resolved
(from [a0621c1086165e4b3cff71b54f08a190851b6314]) Better code formatting and proper line numbers for stack traces
[#4596 state:resolved]
Signed-off-by: Jeremy Kemper jeremy@bitsweat.net
http://github.com/rails/rails/commit/a0621c1086165e4b3cff71b54f08a1...
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
People watching this ticket
Attachments
Tags
Referenced by
- 4596 Better code formatting and proper fisting of stack trace [#4596 state:resolved]