Philip Martin wrote:
> Julian Foad writes:
> > Philip Martin wrote:
> >> http://subversion.tigris.org/issues/show_bug.cgi?id=4042
> > [...] Should we support that in 1.7? Or should we simply have the
> >> client refuse to commit incomplete nodes. Most incomplete nodes
> >> occur after an interru
Julian Foad writes:
> Philip Martin wrote:
>> http://subversion.tigris.org/issues/show_bug.cgi?id=4042
> [...] Should we support that in 1.7? Or should we simply have the
>> client refuse to commit incomplete nodes. Most incomplete nodes
>> occur after an interrupted update, but wc could have
Philip Martin writes:
> What does refusing to commit incomplete directories mean. Given:
>
> $ svn st wc
> ! wc/A/B
> M wc/A/B/C/f
> !M wc/X/Y
Typo, I meant
! wc/X/Y
> M wc/X/B/C/f
> M wc/P/f
>
> Do these fail due to incomplete:
>
> $ svn ci wc/A/B/C/f # explict inside incomple
Julian Foad writes:
> Philip Martin wrote:
>> http://subversion.tigris.org/issues/show_bug.cgi?id=4042
> [...] Should we support that in 1.7? Or should we simply have the
>> client refuse to commit incomplete nodes. Most incomplete nodes
>> occur after an interrupted update, but wc could have
Philip Martin wrote:
> http://subversion.tigris.org/issues/show_bug.cgi?id=4042
[...]
> Should we support that in 1.7? Or should we simply have the client
> refuse to commit incomplete nodes. Most incomplete nodes occur
> after an interrupted update, but wc could have incomplete working
> nodes
A user reported an assertion failure in 1.7:
http://subversion.tigris.org/issues/show_bug.cgi?id=4042
caused by committing a property change on a presence=incomplete
directory. It's not possible to prevent property modifications on
incomplete directories, since the modification could be made bef
6 matches
Mail list logo
