On Wed, Mar 26, 2014 at 4:29 AM, Daniel Shahaf wrote:
> stef...@apache.org wrote on Tue, Mar 25, 2014 at 23:12:03 -:
> > +
> > +Incompatibility
> > + > +title="Link to this section">¶
> > +
> > +
> > +The FSX code and storage representation is incomplete with respect to
> > +the feature
Julian Foad writes:
> Hi Philip...
>
>> URL: http://svn.apache.org/r1577280
>> Log:
>> Merge the fsfs-lock-many branch to trunk. [...]
>
>> * subversion/include/svn_fs.h
>> (svn_fs_lock_target_t, svn_fs_lock_result_t,
>> svn_fs_lock2, svn_fs_unlock2): new.
>>
>> * subversion/include/svn_re
Philip Martin wrote:
> Issue 4412 http://subversion.tigris.org/issues/show_bug.cgi?id=4412 is a
> serf bug that causes the client to incorrectly remove locks from the
> working copy during update.
[...]
> I propose to remove this compatibility code from 1.8 and trunk. This
> will fix the 4412 prob
Issue 4412 http://subversion.tigris.org/issues/show_bug.cgi?id=4412 is a
serf bug that causes the client to incorrectly remove locks from the
working copy during update. This bug is seen when using a 1.8 client
with a 1.6.16 or earlier server: locks get removed from the working copy
but are still
Hi Philip...
> URL: http://svn.apache.org/r1577280
> Log:
> Merge the fsfs-lock-many branch to trunk. [...]
> * subversion/include/svn_fs.h
> (svn_fs_lock_target_t, svn_fs_lock_result_t,
> svn_fs_lock2, svn_fs_unlock2): new.
>
> * subversion/include/svn_repos.h
> (svn_repos_fs_lock2, svn
Bert Huijben wrote:
>> Shouldn't we have an EOL-style translation option as well? Usually the
>> two go together.
>
> Not sure.
>
> svn_client_cat2() already implemented keyword expansion, but I don't think
> it changes EOL?
>
>
> I just added an option to allow disabling a magic feature of
>
> -Original Message-
> From: Julian Foad [mailto:julianf...@btopenworld.com]
> Sent: woensdag 26 maart 2014 12:57
> To: Bert Huijben
> Cc: dev@subversion.apache.org
> Subject: Re: svn commit: r1544182 - in /subversion/trunk/subversion:
> include/svn_client.h libsvn_client/cat.c libsvn_cli
Hi Bert...
> URL: http://svn.apache.org/r1544182
> Log:
> Make the 'svn_client_cat()' API a bit more generic usable for api users,
> by allowing the suppression of keyword expansion and by optionally returning
> the properties of the node.
Shouldn't we have an EOL-style translation option as wel
> -Original Message-
> From: Daniel Shahaf [mailto:d...@daniel.shahaf.name]
> Sent: woensdag 26 maart 2014 04:21
> To: dev@subversion.apache.org
> Cc: comm...@subversion.apache.org
> Subject: Re: svn commit: r1580866 - in
> /subversion/trunk/subversion/svnrdump: load_editor.c svnrdump.c
>
Bert Huijben wrote:
> Doesn't svnsync do something similar?
svnsync normalizes EOL style of all svn:* props, but nothing special for
mergeinfo.
I found this issue while investigating issue #4476 "Mergeinfo containing r0
makes svnsync and svnadmin dump fail". I was considering adding such proces
10 matches
Mail list logo
