With the new patch features from 1.7 would it make sense to implement this
feature internally as a stored patch with some extra changes to the client
to allow exporting the shelved changes as a patch and more obviously shelve
and unshelve?
As a TortoiseSVN user I'm thinking such feature could be a
On 06.09.2011 23:45, Daniel Shahaf wrote:
> How should the fs-successor-ids branch's new functionality be reflected
> in the API and the public API?
>
> The basic question is "Given PATH@REV, will it be moved or copied in the
> future?", and the use-cases Stefan has also boil down to that.
>
> - Wh
On Tue, May 24, 2011 at 12:35 PM, wrote:
> Author: stsp
> Date: Tue May 24 16:35:14 2011
> New Revision: 1127134
>
> URL: http://svn.apache.org/viewvc?rev=1127134&view=rev
> Log:
> As part of issue #3779, "actual-only nodes need regression tests",
> make 'svn add' detect tree conflict victims tha
How should the fs-successor-ids branch's new functionality be reflected
in the API and the public API?
The basic question is "Given PATH@REV, will it be moved or copied in the
future?", and the use-cases Stefan has also boil down to that.
- What operations should the API report?
Modification
On Tue, Sep 06, 2011 at 06:42:44PM +0300, Daniel Shahaf wrote:
> r1165700 mentions that we need to decide what to do with 'svnadmin
> upgrade'.
>
> 1. We could punt and require a dump/load. All format >=6 FSFS instances
>always have a full successors store.
>
> 2. We could store the progeny
That's the tool I had in mind, but to "lazily populate the cache" is
the tricky bit.
Mark Phippard wrote on Tue, Sep 06, 2011 at 11:50:40 -0400:
> If it makes any sense, you could look at what we did in 1.5 for merge
> tracking.
>
> Merge tracking required a new bit of information -- the node or
If it makes any sense, you could look at what we did in 1.5 for merge tracking.
Merge tracking required a new bit of information -- the node origin
index. Dump/Load automatically populated this index. svnadmin
upgrade bumped the format but did not populate the index. Instead the
index was lazil
ne...@apache.org writes:
> Author: neels
> Date: Sat Sep 3 02:49:16 2011
> New Revision: 1164796
>
> URL: http://svn.apache.org/viewvc?rev=1164796&view=rev
> Log:
> * STATUS: Nominate branches/1.7.x-issue4000.
>
> Modified:
> subversion/branches/1.7.x/STATUS
>
> Modified: subversion/branches/
r1165700 mentions that we need to decide what to do with 'svnadmin
upgrade'.
1. We could punt and require a dump/load. All format >=6 FSFS instances
always have a full successors store.
2. We could store the progeny shard size and the successors data shard
size in the 'format' file. If th
> What repository do you mean by "from it" and "here".
> Is it in both source and target repositories that you are sync'ing, or
> you have looked only into one of them?
I mean that i can checkout revision in question of SOURCE repository (in
terms of subversion it's a repository i'm cloning FROM).
On Tue, Sep 6, 2011 at 9:33 AM, Philip Martin
wrote:
> Philip Martin writes:
>
>> I think we should raise an issue.
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=4008
Agreed. Thanks for raising it.
-Hyrum
--
uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com/
Philip Martin writes:
> I think we should raise an issue.
http://subversion.tigris.org/issues/show_bug.cgi?id=4008
--
uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com
Hyrum K Wright writes:
> I tried this again using serf, and a WC->REPO copy works just fine; it
> only fails on a REPO->REPO copy.
>
>> Any clues in the server error log?
>
> The server log gives:
> [Tue Sep 06 08:12:02 2011] [error] [client xxx.xxx.xxx.79] Querying
> mergeinfo requires version 3
On Tue, Aug 30, 2011 at 4:42 AM, Philip Martin
wrote:
> Hyrum K Wright writes:
>
>> In an effort to make sure my problems with serf are well known, I'm
>> posting this. I'm attempting to create a tag of a personal project,
>> and get the following error (over https, with the 1.7.x branch):
>>
>>
This thread belongs on us...@subversion.apache.org. This list is devoted to
discussion about the development of the Subversion software itself. Thanks!
On 09/06/2011 06:53 AM, Grigory Petrov wrote:
> Hello.
>
> I'm mirroring one of my repositories right now. Repository is hosted with
> subvers
Thanks Prabhu. Committed this patch in r1165631.
With regards
Kamesh Jayachandran
-Original Message-
From: Prabhu Gnana Sundar Ponnarasu
Sent: Tue 9/6/2011 12:33 PM
To: Kamesh Jayachandran
Cc: Vijayaguru Guruchave; dev@subversion.apache.org
Subject: Re: [PATCH] get-location-segments.py wo
2011/9/6 Grigory Petrov :
> Hello.
> I'm mirroring one of my repositories right now. Repository is hosted with
> subversion 1.6.x and my client is sliksvn 1.6.17. The "svnsync" command
> synchronize most of the repository but at some point it fails with:
> Transmitting file data ...svnsync: File no
Hello.
I'm mirroring one of my repositories right now. Repository is hosted with
subversion 1.6.x and my client is sliksvn 1.6.17. The "svnsync" command
synchronize most of the repository but at some point it fails with:
Transmitting file data ...svnsync: File not found: transaction '12893-qyy',
Hi, Julian,
Von: Julian Foad [mailto:julian.f...@wandisco.com]
> Hi Markus. Thanks for this report, and sorry for the slow response.
Thanks for answering, nowadays its holidays time. :-)
> There are two different problems here.
>
>
> On Mon, 2011-08-29, Markus Schaber wrote:
> > (This is a sl
Updated/fixed the script to not prompt the certificate even if the
certificate is accepted permenantly, similar to the
get-location-segments.py script.
Attaching the updated script.
Thanks and regards
Prabhu
On Friday 19 August 2011 11:45 AM, Prabhu Gnana Sundar wrote:
Correcting the issu
> -Original Message-
> From: Julian Foad [mailto:julian.f...@wandisco.com]
> Sent: dinsdag 6 september 2011 11:24
> To: Markus Schaber
> Cc: dev@subversion.apache.org
> Subject: Re: Inconsistencies in svn_client_info_3
>
> Hi Markus. Thanks for this report, and sorry for the slow respon
Hi Markus. Thanks for this report, and sorry for the slow response.
There are two different problems here.
On Mon, 2011-08-29, Markus Schaber wrote:
> (This is a slightly enhanced repost.)
>
> I'm using latest build of SharpSVN against SVN 1.7.
(To be accurate: you must be using some release
On Monday 05 September 2011 05:44 PM, Kamesh Jayachandran wrote:
Prabhu,
One small problem with your patch.
See the below snip
[kamesh@kamesh trunk]$ python tools/examples/get-location-segments.py
https://svn.eu.apache.org/repos/asf/subversion/trunk
The certficate details are as follows:
--
23 matches
Mail list logo
