Hey Stefan, Hyrum,
I have read the following files recently and I have some questions:
4) Read the "State of the WC-NG World" thread on dev@
>In the thread "State of the WC-NG World" gstein said
>"It is being replaced with svn_wc_context_t which is constructed once and
>used for all operations across all directories and even across
>distinct working copies. Essentially, a process can create one at
>startup and use it for all calls."
But how can we use svn_wc_context_t across distinct working copies?
svn_wc_context_t is an opaque structure which contains a pointer to an
svn_wc__db_t. As I understand we have one-db-per-working copy right
now. So if we want to use svn_wc_context_t across distinct wc, should
it contain multiple svn_wc__db_t?
>Another big change is removing the old "loggy" mechanism in favor of a
>sqlite-based queue of operations to perform (essentially where we need
>to "transact" changes across sqlite and the filesystem).
I saw work_queue table in libsvn_wc/wc-metadata.sql and I do not know
what "work" really is. Is it the same thing as "sqlite-based queue of
operations" mentioned above?
I am tring to follow the dev@ and svn@ maillist. But some topics in them are
a little hard for me to understand and it takes me lot of time to read them.
Any good suggestions to deal with the mails? :)
I am not very clear on where to begin my new work right now. My plan is in
the next few days:
1) Read more docs and make myself more clear about wn-ng.
2) Try to remove svn_wc_entry_t and svn_wc_adm_access_t reference in
libsvn_wc and libsvn_client, especially in functions about commit, and use
3) Try to understand how can we do commit based on wc-ng.
Received on 2009-07-26 10:29:06 CEST