On Fri, Mar 23, 2001 at 09:19:32AM -0500, Derek R. Price wrote:
> Nathan Herring wrote:
> > Import knows the name and branch version of the vendor branch, has a
> > list of files to import, and has a list of files already in the
> > repository. This is all it needs to know. Now use the following
> > heuristic:
>
> Basically, import would have to look up the tip of the vendor branch
> before execution to obtain the list of files present during the last
> import.
Not "before execution". Instead, "import" turns into a classic
merge(*) -- which I guess "update" already is. So one has to add
a scan of the repository directory, and the reading of any
repository files that aren't in the directory being imported, but
it's still only one-pass.
* I mean "merge" here in the traditional "sort/merge" sense,
not CVS's "merging revisions" sense -- don't you love
overloaded jargon?
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont. [EMAIL PROTECTED]
| | /
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea.
- RFC 1925 (quoting an unnamed source)
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
