The thing is, having such working copies can be a real pain when you have a
large source tree, 1gb (2gb as working copy). Some users don't like having
multiple 2gb copies of the source around, and even if they did would prefer
to have a nice way to check for updates on just subgroups of the source tree
that might span multiple directories.
One WC per task may be the ideal, but the ideal doesn't always make sense.
- Jody
On 10/18/05, Björn Eriksson <owbear@gmail.com> wrote:
>
> Greetings Aniruddha,
>
> Aniruddha Apte <aniapte <at> gmail.com <http://gmail.com>> writes:
> > Here is a description of "Commit Groups". Please suggest a new name if
> > this is confusing.
> >
> > 1. "Commit Groups" will be a new dialog. This would be a tool to
> > logically segregate working copy (or unversioned) files into groups
> > that can be managed.
>
> There's a better way: one wc per task.
>
> "... a recommended workflow where every developer concentrates on a single
> task(let)/issue: plan, code, test and commit.
>
> Thus, the perfect programmer writes his commit message(s) before even
> starting
> work!"
>
> are the rules we use here.
>
>
> I think stageing the commit in logical groups of files - with a
> temporarily
> broken tree - is a fix for a situation that shouldn't have occured in the
> first
> place.
>
>
> --
> //Björnen
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
>
>
Received on Thu Oct 20 16:25:50 2005