Julian Foad wrote on 2018-11-09:
> > Implementation of the "WC delta editor" is in progress.
>
> Currently factoring out our "copy dir from repos to WC" implementation
Some more notes on progress.
The way we handle "copy" into the WC is a beast. Untangling this is by far the
most complex part
Greg Stein wrote:
>> Is this such a crazy idea?
>
> Not at all. This is what Ev2 was supposed to do. Part of my work
> around that was to start shifting code from the old delta-editor to
> Ev2. We have shims already available to support that work. I'd suggest
> looking at Ev2 rather than creating
On Fri, Nov 9, 2018 at 4:56 AM Julian Foad wrote:
>...
> Is this such a crazy idea?
>
Not at all. This is what Ev2 was supposed to do. Part of my work around
that was to start shifting code from the old delta-editor to Ev2. We have
shims already available to support that work. I'd suggest lookin
Julian Foad wrote on Fri, 09 Nov 2018 10:56 +:
> It is really quite important for the feasibility of writing higher level
> code such as shelving, that WC modifications can be read and written by
> a common, abstract, interface. That is, an interface definition which
> enables a 'copy' funct
Julian Foad wrote:
> The "WC replay delta" is simple and about ready to commit.
r1846252.
> Implementation of the "WC delta editor" is in progress.
Currently factoring out our "copy dir from repos to WC" implementation from
these two places:
libsvn_client/copy.c : repos_to_wc_copy_single()
li
Branko Čibej wrote:
> The WC-NG with its multiple op-depths behaves like a
> limited-history repository. Your picture does lack the op-depth part,
> though; there are N layers between BASE and WORKING, unlike in the
> filesystem, where we always work against a single (base) revision.
I don't think
On 09.11.2018 11:56, Julian Foad wrote:
> Is this such a crazy idea?
Not at all. The WC-NG with its multiple op-depths behaves like a
limited-history repository. Your picture does lack the op-depth part,
though; there are N layers between BASE and WORKING, unlike in the
filesystem, where we always
The WC's main job is to compose a new revision.
While the WC also supports merge conflict resolution, a mixed-revision base
state, commit of selected parts, and many other additional features, the
fundamental purpose of the WC is to help the user prepare, review and commit a
set of changes whic
8 matches
Mail list logo
