Julian Foad wrote:
> Greg Stein wrote:
>> When I envisioned the implementation of shelving, I figured that we would
>> use the sql database to its best effect.
Let me be more concrete.
>> Store new pristines (which is logically just key->fulltext).
Pristine file texts add up to a large fractio
Stefan Kueng wrote:
> A few more thought, mostly for the next release:
>
> * svn_client_shelf_save_new_version3 takes two callback functions, but
> they both have the same type. So why not just change that API to take
> one callback but provide a 'failed' flag instead?
Could do! I suppose that
A few more thought, mostly for the next release:
* svn_client_shelf_save_new_version3 takes two callback functions, but
they both have the same type. So why not just change that API to take
one callback but provide a 'failed' flag instead?
* when a shelve operation fails, we have to remove th
Julian Foad wrote:
> [...] Flat files (no longer flat files) are easier to mess with at
> this stage.
I meant, "Flat files (no longer patch files)...".
- Julian
Greg Stein wrote:
> When I envisioned the implementation of shelving, I figured that we
> would use the sql database to its best effect. Store new pristines
> (which is logically just key->fulltext). Maybe create an artificial
> wc_id to construct an alternate tree of ACTUAL_NODE entries where you
On Sat, Sep 15, 2018 at 4:03 AM Julian Foad wrote:
>...
> > * when users update to the new version, existing shelves can't be used
> > anymore since they're not compatible. Is there a way to convert the old
> > shelves to the new format? If not then that means users would lose those
> > saved she
Stefan Kueng wrote on 2018-09-15:
> Hi,
>
> I know I'm a little bit late, but now I'm implementing the new shelf
> APIs in TSVN so it's now that I have some thoughts and suggestions:
>
> * there are deprecated APIs already, even though they weren't there in
> 1.10.0, for example svn_client
7 matches
Mail list logo
