On 03/14/2010 03:11 PM, Philip Martin wrote:
Karthik K writes:
Wondering if there is a document explaining the svn:// uri
connection protocol ( among other transports/protocols that svn
supports, primarily interested in the read-only checkouts), and
clients that implement the protocol
hi svn dev team -
Wondering if there is a document explaining the svn:// uri
connection protocol ( among other transports/protocols that svn
supports, primarily interested in the read-only checkouts), and clients
that implement the protocol.
--
Karthik.
Karthik K writes:
> Wondering if there is a document explaining the svn:// uri
> connection protocol ( among other transports/protocols that svn
> supports, primarily interested in the read-only checkouts), and
> clients that implement the protocol.
How about:
C
http://svn.apache.org/repos/a
hi svn dev team -
Wondering if there is a document explaining the svn:// uri
connection protocol ( among other transports/protocols that svn
supports, primarily interested in the read-only checkouts), and clients
that implement the protocol.
--
Karthik.
Philip Martin writes:
> Any improvement is lost in
> the noise when I run the command line client on Linux.
As measured by CPU usage or runtime.
--
Philip
Johan Corveleyn writes:
> On Tue, Mar 9, 2010 at 8:04 PM, Julian Foad wrote:
>> On Sun, 2010-03-07, Stefan Fuhrman wrote:
>>> Speed up input stream processing in config parser and
>>> others that read single bytes from a stream.
>>>
>>> * subversion/libsvn_subr/subst.c
>>> (translated_stream_r
On Tue, Mar 9, 2010 at 8:04 PM, Julian Foad wrote:
> On Sun, 2010-03-07, Stefan Fuhrman wrote:
>> Speed up input stream processing in config parser and
>> others that read single bytes from a stream.
>>
>> * subversion/libsvn_subr/subst.c
>> (translated_stream_read): Add an optimized code path
>
On Fri, Mar 12, 2010 at 07:42:53PM -0600, Hyrum K. Wright wrote:
> On Mar 12, 2010, at 3:52 PM, Daniel Näslund wrote:
> >>> - if (status->entry->depth != svn_depth_exclude)
> >>> + /* Added files have a revision of no interest */
> >>> + if (revision != SVN_INVALID_REVNUM)
> >>> {
> >>> -
Hi!
The 1.6 svnversion message was "'path' not versioned, and not exported".
But on trunk more than one message has been changed. My first thought
was that we should be backward compat in our output but if changes of
those messages are ok I'm supplying one.
In case we will use new messages, the h
"Bert Huijben" writes:
> http://buildbot.subversion.org/buildbot/waterfall still says that the svn x
> fsfs build testsuite is broken.
> (This buildbot uses a recent trunk for checking out the build working
> copy... that could make a difference for the specific test)
$ cd subversion/tests/cmdli
> -Original Message-
> From: Philip Martin [mailto:philip.mar...@wandisco.com]
> Sent: zondag 14 maart 2010 19:10
> To: Bert Huijben
> Cc: dev@subversion.apache.org; phi...@apache.org
> Subject: Re: svn commit: r922511 -
> /subversion/trunk/subversion/libsvn_client/commit.c
>
> "Bert Hui
"Bert Huijben" writes:
>> New Revision: 922511
>>
>> URL: http://svn.apache.org/viewvc?rev=922511&view=rev
>> Log:
>> Remove access batons from client commit code.
>>
>> * subversion/libsvn_client/commit.c
>> (struct check_dir_delete_baton): Remove access baton.
>> (check_nonrecursive_dir_d
> -Original Message-
> From: phi...@apache.org [mailto:phi...@apache.org]
> Sent: zaterdag 13 maart 2010 10:27
> To: comm...@subversion.apache.org
> Subject: svn commit: r922511 -
> /subversion/trunk/subversion/libsvn_client/commit.c
>
> Author: philip
> Date: Sat Mar 13 09:27:20 2010
>
"Bert Huijben" writes:
>> From: Philip Martin [mailto:philip.mar...@wandisco.com]
>>
>> I'd like 'svn status' to start indicating when a working copy is
>> sparse, probably by using 'P' like svnversion. It could also be used
>> to indicate not-present nodes.
>
> Where would you like it to repor
> -Original Message-
> From: Philip Martin [mailto:philip.mar...@wandisco.com]
> Sent: zondag 14 maart 2010 14:38
> To: Greg Stein
> Cc: dev@subversion.apache.org
> Subject: Re: svn commit: r921445 - in /subversion/trunk/subversion:
> include/private/svn_wc_private.h include/svn_wc.h
> li
Greg Stein writes:
> Rather than explicit acquire/release, I think we're trying to use
> svn_wc__call_with_write_lock(). That will ensure that we don't leave
> write locks around on an error exit.
I've used svn_wc__call_with_write_lock in the past but I feel that the
baton interface is cumbersom
Greg Stein writes:
> $ svn rm path/subdir
> $ svn commit path/subdir
> $ svnversion
>
> Should it report "just r9", or should it report "r9-10" ?
We could change the definition of r9P to include not-present as well
as excluded.
I'd like 'svn status' to start indicating when a working copy is
sp
On Fri, Mar 12, 2010 at 10:00:48AM +0100, Stefan Sperling wrote:
> On Tue, Mar 09, 2010 at 03:01:36PM +, Justin Erenkrantz wrote:
> > On Tue, Mar 9, 2010 at 9:59 AM, Stefan Sperling wrote:
> > > Does this mean that we don't have to do anything special to apply
> > > for Gsoc, but just apply fo
On Sun, Mar 14, 2010 at 1:00 AM, Greg Stein wrote:
> On Fri, Mar 12, 2010 at 06:28, Philip Martin
> wrote:
>> Greg Stein writes:
>>
>>> The SUBDIR is a child of DIR in r9, and presumably also r6. When the
>>> commit is performed, constructing r10, SUBDIR is deleted. The working
>>> copy lists D
19 matches
Mail list logo
