Thorsten Scherler wrote:
On Sat, 2005-08-27 at 14:51 +0100, Ross Gardler wrote:
David Crossley wrote:
Thorsten Scherler wrote:
c) refactoring of "old" code into a new version which would break the
usability of the old code while refactoring.
I think that would be better done in a branch
On Sat, 2005-08-27 at 14:51 +0100, Ross Gardler wrote:
> David Crossley wrote:
> > Thorsten Scherler wrote:
> >
> >>c) refactoring of "old" code into a new version which would break the
> >>usability of the old code while refactoring.
> >
> >
> > I think that would be better done in a branch.
>
David Crossley wrote:
Thorsten Scherler wrote:
c) refactoring of "old" code into a new version which would break the
usability of the old code while refactoring.
I think that would be better done in a branch.
+1
Ross
Thorsten Scherler wrote:
> c) refactoring of "old" code into a new version which would break the
> usability of the old code while refactoring.
I think that would be better done in a branch.
-David
On Fri, 2005-08-26 at 12:28 -0400, Tim Williams wrote:
> Can someone describe the intended use of the whiteboard in our svn?
> Is it a committers playground for project-related stuff? I'm unclear
> when it should be used.
> Thanks,
> --tim
In lenya we call it sandbox which sounds like your playg
Tim Williams wrote:
Can someone describe the intended use of the whiteboard in our svn?
Is it a committers playground for project-related stuff? I'm unclear
when it should be used.
You know, this is a really good question. I don't know that we have ever
actually defined what it is used for.
