Re: Clearly setting apart the code we want to replace?

[Michael Richardson <..hidden..>]

Erik Huelsmann <..hidden..> wrote:
    > The source code in our project falls into two categories:

    > 1. the code we newly wrote (and which we want to maintain) 2. the code
    > that we inherited (and which we want to replace)

    > Where to find code of the first and the second category, is pretty
    > clear to most of us. However, it's not to any new-comers to the
    > project.  In order to improve this clarity - making it easier to
    > communicate about it - I'm proposing to move all *library* code that we
    > intend to replace from lib/ to old/, meaning

Yes.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     ..hidden..  http://www.sandelman.ca/        |   ruby on rails    [


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Ledger-smb-devel mailing list
..hidden..
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel