#4596 Better code formatting and proper fisting of stack trace - Ruby on Rails

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

This project is archived and is in readonly mode.

#4596 ✓resolved

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...

Neeraj Singh May 14th, 2010 @ 08:12 PM
- Assigned user set to “Jeremy Kemper”
Attached is patch.
- 4596_fix.patch 6.6 KB
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...

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>