RE: commit crawler

Something similar is required in order to get the correct list of
permission request to pass to a "check all of these permissions" hook.
(Although probably in a completely different chunk of code)

Bill

--
Bunnies aren't just cute like everybody supposes.
They got their hoppy legs and twitchy little noses.
And what's with all the carrots, 
What do they need such good eyesight for anyway?
-----Original Message-----
From: cmpilato@collab.net [mailto:cmpilato@collab.net] 
Sent: Friday, November 16, 2001 11:34 AM
To: sussman@collab.net
Cc: dev@subversion.tigris.org
Subject: commit crawler
Hey, Ben.  Was wondering what you thought about us changing the commit
crawler so that mined information from the working copy first, storing
relavent bits in some applicable in-memory data structure and locking
dirs and such, then blew through that data structure to perform the
actual commit.
Reason I ask is that I'd like to recycle alot of the logic in that
commit process, but for working-copy-free commits (like `svn cp' is
soon to do).  It'd be great if svn_wc_crawl_local_mods simply
generated some Thing that, when passed to a commit editor driver,
could perform a commit.  That way our working-copy-less commits could
simply manufacture their own Things, and pass those off to the same
driver.
Plus, I think it would help the commit crawler not be such a mess, to
seperate the local-mod search from the commit process itself.
Just polling for thoughts here.  Lemme know.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org