Hi Stefan,
stef...@apache.org wrote on Mon, Jul 26, 2010 at 08:30:08 -:
> Author: stefan2
> Date: Mon Jul 26 08:30:08 2010
> New Revision: 979193
>
> URL: http://svn.apache.org/viewvc?rev=979193&view=rev
> Log:
> Provide a memcached-like implementation of svn_cache_t that does not have
> the
C. Michael Pilato wrote on Tue, Jul 27, 2010 at 10:47:21 -0400:
> On 07/27/2010 10:26 AM, Ivan Zhakov wrote:
> > On Tue, Jul 27, 2010 at 17:42, C. Michael Pilato
> > wrote:
> >> On 07/27/2010 03:08 AM, Daniel Shahaf wrote:
> >>> For the atomic-revprop branch, the next step is to implement the new
On Tue, Jul 27, 2010 at 1:36 PM, Daniel Shahaf wrote:
> Paul Burba wrote on Tue, Jul 27, 2010 at 11:50:55 -0400:
>> * If you happen to look, I'll save you some trouble since this struct
>> is undocumented, it's a (svn_revnum_t) key mapped to a hash which maps
>> a (const char *) url (or path) to a
Paul Burba wrote on Tue, Jul 27, 2010 at 11:50:55 -0400:
> * If you happen to look, I'll save you some trouble since this struct
> is undocumented, it's a (svn_revnum_t) key mapped to a hash which maps
> a (const char *) url (or path) to a hash, which maps a (const char *)
> namespace to a hash, wh
Hi Daniel,
Ramkumar Ramachandra writes:
> Daniel Shahaf writes:
> > I suggest
> >
> > fromfile="EXPECTED %s" % label,
> > tofile="ACTUAL %s" % label,
>
> Do I get a +1 for this?
I just got one from Bert. Committed in r979710.
Thanks.
-- Ram
svnusert...@href.com wrote:
> Hi Julian et al,
>
> Yes, the new 1.7 feature sounds very promising. I was wondering what
> WC-NG stands for but I think I get the idea.
[...]
> I'll tell you the one way in which that might not completely solve
> the use-case that I have in mind, and that is doing
Re. patches being stripped from the mail:
svnusert...@href.com wrote:
> I tried sending the rest of this reply earlier and suspect it was
> caught in a moderator queue. (( I'm subscribed now; take 2 and
> apologies for anyone who has already read this. I suspect that my
> .patch files (which
[[[
Followup r979295 to handle the expected_is_regexp case in
display_lines.
* subversion/tests/cmdline/svntest/verify.py
(display_lines): When expected is a string and not a list (in the
expected_in_regexp case), put it in a one-member list, and don't
output a diff.
Found by: rhuijben
]]]
[[[
svnrdump: Add new copy-and-modify test.
* subversion/tests/cmdline/svnrdump_tests_data/copy-and-modify.dump:
Add a new testdata to be used by the copy_and_modify test in
svnrdump. Taken originally from svnsync_test_data/ and converted to
dumpfile v3 format.
* subversion/tests/cmdline/sv
On Fri, Jul 23, 2010 at 2:30 PM, C. Michael Pilato wrote:
> On 07/22/2010 05:56 PM, Paul Burba wrote:
>> On Thu, Jul 22, 2010 at 5:04 PM, Bert Huijben wrote:
>>> Shouldn't this be fixed in the ra layer implementations then?
>>
>> From what Mike told me in
>> http://subversion.tigris.org/issues/sh
> Yes, the new 1.7 feature sounds very promising. I was wondering
> what
> WC-NG stands for but I think I get the idea.
Working Copy Next Generation
BOb
Hi Julian et al,
Yes, the new 1.7 feature sounds very promising. I was wondering what
WC-NG stands for but I think I get the idea.
I tried sending the rest of this reply earlier and suspect it was
caught in a moderator queue. (( I'm subscribed now; take 2 and
apologies for anyone who has a
On 07/27/2010 10:26 AM, Ivan Zhakov wrote:
> On Tue, Jul 27, 2010 at 17:42, C. Michael Pilato wrote:
>> On 07/27/2010 03:08 AM, Daniel Shahaf wrote:
>>> For the atomic-revprop branch, the next step is to implement the new API
>>> (svn_ra_change_rev_prop2()) over ra_svn and ra_dav.
>>>
>>> For ra_s
On Tue, Jul 27, 2010 at 12:10:55AM +0530, Ramkumar Ramachandra wrote:
> Hi Stefan,
>
> I imported and ran the copy_and_modify test from svnsync. The diff I
> get clearly indicates what more needs to be done, and I think this
> test is very valuable. Unfortunately, `svn diff` refuses to show me
> t
On Tue, Jul 27, 2010 at 17:42, C. Michael Pilato wrote:
> On 07/27/2010 03:08 AM, Daniel Shahaf wrote:
>> For the atomic-revprop branch, the next step is to implement the new API
>> (svn_ra_change_rev_prop2()) over ra_svn and ra_dav.
>>
>> For ra_svn, I'll document the protocol extensions in
>> .
On 07/27/2010 03:08 AM, Daniel Shahaf wrote:
> For the atomic-revprop branch, the next step is to implement the new API
> (svn_ra_change_rev_prop2()) over ra_svn and ra_dav.
>
> For ra_svn, I'll document the protocol extensions in
> .
>
> Where should I document the extensions for the DAV protoc
Hi Daniel,
Daniel Shahaf writes:
> I suggest
>
> fromfile="EXPECTED %s" % label,
> tofile="ACTUAL %s" % label,
Do I get a +1 for this?
[[[
* subversion/tests/cmdline/svntest/verify.py
(display_lines): Improve diff output by displaying `message` along
with the header.
Suggested
I agree with everything Stefan says here: I think it's not appropriate
to include this particular feature, but thank you for offering your work
back to the community and hope that you will keep on doing so.
I'll also note that we are developing in a direction which will probably
help you in the fu
Colleagues,
I have subversion-1.6.12 compiled with cyrus-sasl-2.1.23 from ports,
FreeBSD 6.4.
I need to guarantee that the subversion client/server will always use
the GSSAPI mechanism before DIGEST-MD5. In a more general sense, one
may need to set the order of SASL mechanisms for authenticated
For the atomic-revprop branch, the next step is to implement the new API
(svn_ra_change_rev_prop2()) over ra_svn and ra_dav.
For ra_svn, I'll document the protocol extensions in
.
Where should I document the extensions for the DAV protocol?
Thanks,
Daniel
(I plan to add an tag nested under t
20 matches
Mail list logo
