RE: Newly added files listed as Unknown

If you set your working folder to the location on disk where your files are,
the files get added in a known state.  If you set the working folders after
you add the files, then they are in an unknown state.  Automatically setting
the working folder on an Add would probably surprise some users in a bad
way.  However, offering to set a working folder before an add (if it isn't
already set), would probably be a considerate thing to do.  I'll add that as
a feature request.

The real problem here is that Vault gives up very easily on Unknown files,
and never attempts to reconcile them with what's in the database.  That's a
more long term solution that we have on the list too.

-Dan

> -----Original Message-----
> From: vault-list-admin@xxxxxxxxxxxxxxxxxxxx
> [mailto:vault-list-admin@xxxxxxxxxxxxxxxxxxxx]On Behalf Of Mike Dimmick
> Sent: Friday, January 23, 2004 7:12 PM
> To: 'Vault-List'
> Subject: [vault-list] Newly added files listed as Unknown
>
>
> I'm afraid I find this annoying: when I add a new file to the repository,
> the local file status is shown as Unknown. I have to do a Get Latest in
> order for it to show as up-to-date - and when I do, Vault backs up all of
> the local files, even though they've not changed.
>
> Could Vault create the local state at the point of adding the
> files, and set
> the working directory initially to the directory they were added from (at
> least in the case where folders are being created)?
>
> Obviously this is an issue when migrating baselines not previously under
> source control, or using a tool other than SourceSafe.
>
> Thanks,
>
> --
> Mike Dimmick
>
>
> _______________________________________________
> vault-list mailing list
> vault-list@xxxxxxxxxxxxxxxxxxxx
> http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list