Hi,
This way TortoiseSVN loses a way of creating branches from working copy
without accidental errors. A simple warning would be sufficient to remind,
that you have nont-added files on working copy and your branch will not
reflect state of your working copy (as it is for compiler - not for SVN). I
understand why you say that suggested is not good solution, but propable it
is good idea to have separate dialog for creating branch from working copy,
as it is quite different to branches from repository.
Sample scenario is creating snapshots of working copy to refer them in bug
tracker and it is quite annoying t find later that these snapshots miss some
files.
thank you
Yuriy
> Yuriy Solodkyy wrote:
> > Hi,
> >
> > I find find quite uncomfortable that branch dialog does not provide the
> > same service for adding files as commit dialog when used to create a
> > branch from working copy. Branch from working copy is often used to
> > cerate personal branch or branch to transfer changes to another
> > developer and you often need to add new files in working copy before
> > making the branch. It is very convinient that commit window suggest
> > adding files, but unfortunatelly branch from working copy does not event
>
> > say that you forgot to add those files before making the branch.
> >
> > Hope, this can be implemented some time..
>
> When branching/tagging, the working copy does not change. Which means we
> can't just add unversioned files and then do the tagging. That would
> leave added files in your working copy which you might want to keep
> unversioned.
>
> Also, the branch/tag dialog is already crowded with control where the
> user has to enter information. I don't think it would be better if we
> would add a file list there too.
>
> Stefan
>
> --
> ___
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest Interface to (Sub)Version Control
> /_/ \_\ http://tortoisesvn.net
>
Received on 2008-01-28 15:33:18 CET