> "Fernandes, Filipe (Bolton)" <ffernandes@husky.ca> Wrote:
> > Ah... It's becoming clear to me. I thought I knew what was happening
> until I
> > read your two e-mails more carefully. I envisioned the feature simply
> > converting a folder into a working copy. What I mean by this is that
> the
> > .svn folder is populated throughout the project as follows...
> >
> > 1) tolerating those files that already exist
> >
> > 2) adding the .svn folder to those folders that already exist
> (effectively
> > versioning them and treating pre-existing files as per #1
> >
> > 3) creating those folders that don't exist with checked-out files from
> the
> > repository.
> >
> > Could you let me know if this is 'far' from the truth...? I guess I
> should
> > have involved myself with the mailing list much earlier than this. :(
>
Mark Phippard [mailto:markp@softlanding.com] wrote:
> Those three things sum up the feature that was added to trunk pretty well.
>
Well... that's just awesome then... that's exactly what I'm looking for and
forward to in the 1.5 release (hopefully, praying)...!
And as far as comments made by Paul as to not assuming what the user
wants... I agree, that un-versioned files remain un-versioned (without
scheduled addition), and missing files remain as missing; this certainly
fits the requirements I have at work.
I'm not sure what Giovanni's use case is but if I had to worry about what
just got scheduled for addition and deletion within my working copy as a
result of a checkout, I would definitely find that to be a serious pain.
Although I don't want this to be a comment as to the validity of Giovanni's
argument...
filipe
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 15 19:51:06 2006