Yes, I know I'm the culprit.
The point is, though, that many of my changes start somewhat experimentally,
and I need to be able to *see* what I have removed until it's final. And,
yes, I then often overlook to remove much of that.
My current work on 1856 capitalization again causes pretty much refactoring
and removal of redundant code, so I hope I will do better this time.
Feel free to remove dead code when you see it. And whether you see it or
not, trust me, it's harmless.
Erik.
> -----Original Message-----
> From: Mark Smith [mailto:mar...@gm...]
> Sent: Saturday 15 November 2008 19:43
> To: Development list for Rails: an 18xx game
> Subject: Re: [Rails-devel] [Rails-commits] 18xx/rails/game
> TileI.java, 1.11,1.12 Tile.java, 1.20, 1.21
>
> In this I agree with Brett completely. Given the CVS System, if
> something fails and you need to revert, you can go back to an older
> revision easy enough. It makes the code a lot cleaner to remove "dead
> code" before it is checked in.
>
> Mark
>
> --------------------------------------------------------------
> -----------
> This SF.Net email is sponsored by the Moblin Your Move
> Developer's challenge
> Build the coolest Linux based applications with Moblin SDK &
> win great prizes
> Grand prize is a trip for two to an Open Source event
> anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>
|