Re: [PATCH] Add '--drop-all-empty-revs' to svndumpfilter include/exclude

2013-02-26 Thread Julian Foad
vijay wrote: > Recently, I had a chance to look at a dump file with lot of empty revisions. > The > dump file was taken by syncing a sub-directory of a remote repository using > svnsync. I decided to remove all the empty revisions from the dump file. But > 'svndumpfilter include/exclude --dro

Re: merge test 125 is coredumping

2013-02-26 Thread Julian Foad
  -- Certified & Supported Apache Subversion Downloads: http://www.wandisco.com/subversion/download - Original Message - > From: Philip Martin > To: dev@subversion.apache.org > Cc: > Sent: Monday, 25 February 2013, 5:37 > Subject: Re: merge test 125 is coredumping > > Stefan Sperli

Re: svn commit: r1449428 - /subversion/trunk/subversion/tests/cmdline/tree_conflict_tests.py

2013-02-26 Thread Julian Foad
Bert Huijben wrote: >> URL: http://svn.apache.org/r1449428 >> Log: >> In the tree conflict tests, enable testing with an incoming file >> replacement.  For 'switch', don't test with incoming replacements because >> 'switch' ignores ancestry in its repos diff (unlike 'update') and so does >>

Re: svn commit: r1450341 - /subversion/trunk/subversion/libsvn_client/copy.c

2013-02-26 Thread Philip Martin
Philip Martin writes: > rhuij...@apache.org writes: > >> Author: rhuijben >> Date: Tue Feb 26 18:33:04 2013 >> New Revision: 1450341 >> >> URL: http://svn.apache.org/r1450341 >> Log: >> * subversion/libsvn_client/copy.c >> (wc_to_repos_copy): Temporarily revert the introduction of the session p

Re: BDB deprecation (was: branch 1.8 or at least start making alpha releases?)

2013-02-26 Thread Stefan Fuhrmann
On Wed, Feb 27, 2013 at 12:21 AM, Justin Erenkrantz wrote: > On Tue, Feb 26, 2013 at 1:54 PM, C. Michael Pilato wrote: > >> * The appropriate time to stop supporting Berkeley DB is in the same >> release >> for which existing FSFS will also have to dump/load. It is cruel to force >> admins to end

Re: BDB deprecation (was: branch 1.8 or at least start making alpha releases?)

2013-02-26 Thread Justin Erenkrantz
On Tue, Feb 26, 2013 at 1:54 PM, C. Michael Pilato wrote: > * The appropriate time to stop supporting Berkeley DB is in the same > release > for which existing FSFS will also have to dump/load. It is cruel to force > admins to endure the migration process twice -- possibly in successive > release

Re: svn commit: r1450341 - /subversion/trunk/subversion/libsvn_client/copy.c

2013-02-26 Thread Philip Martin
rhuij...@apache.org writes: > Author: rhuijben > Date: Tue Feb 26 18:33:04 2013 > New Revision: 1450341 > > URL: http://svn.apache.org/r1450341 > Log: > * subversion/libsvn_client/copy.c > (wc_to_repos_copy): Temporarily revert the introduction of the session pool > of r1450279 in an attempt

BDB deprecation (was: branch 1.8 or at least start making alpha releases?)

2013-02-26 Thread C. Michael Pilato
On 02/14/2013 10:23 PM, Branko Čibej wrote: > On 15.02.2013 04:19, Branko Čibej wrote: >> There are other new features in 1.8 that would benefit from having >> potential users (and packagers) look at them sooner rather than later. >> So I'm firmly in the "release alpha from trunk now" camp. > > An

Re: Locking the wc for move-update conflict resolution

2013-02-26 Thread Stefan Sperling
On Tue, Feb 26, 2013 at 10:50:37AM +, Philip Martin wrote: > I prefer solution B and that's what I plan to implement. +1

Re: [PATCH] Add '--drop-all-empty-revs' to svndumpfilter include/exclude

2013-02-26 Thread C. Michael Pilato
On 02/26/2013 10:08 AM, vijay wrote: > If the dump was taken from a mirror repo, r0 might have some information > like 'svn:sync-from-url', 'svn:sync-from-uuid', etc. > I thought that '--drop-all-empty-revs' should not just drop r0 considering > as an empty revision. That's seems fair. The load l

Re: [PATCH] Add '--drop-all-empty-revs' to svndumpfilter include/exclude

2013-02-26 Thread vijay
On Tuesday 26 February 2013 07:47 PM, Philip Martin wrote: vijay writes: /* write out the revision */ /* Revision is written out in the following cases: - 1. No --drop-empty-revs has been supplied. - 2. --drop-empty-revs has been supplied, - but revision has not all nodes d

Re: Locking the wc for move-update conflict resolution

2013-02-26 Thread Branko Čibej
On 26.02.2013 02:50, Philip Martin wrote: > A moved-away-edit tree-conflict occurs when update changes a move > source, so: > > svn mv A/B/C C2 > svn up --accept postpone . > > creates a moved-away-edit conflict on A/B/C. Resolving the conflict > updates C2 by changing the NODES rows and creat

Re: [PATCH] Add '--drop-all-empty-revs' to svndumpfilter include/exclude

2013-02-26 Thread Philip Martin
vijay writes: >/* write out the revision */ >/* Revision is written out in the following cases: > - 1. No --drop-empty-revs has been supplied. > - 2. --drop-empty-revs has been supplied, > - but revision has not all nodes dropped > - 3. Revision had no nodes to begin with.

Locking the wc for move-update conflict resolution

2013-02-26 Thread Philip Martin
A moved-away-edit tree-conflict occurs when update changes a move source, so: svn mv A/B/C C2 svn up --accept postpone . creates a moved-away-edit conflict on A/B/C. Resolving the conflict updates C2 by changing the NODES rows and creating workqueue items to modify the C2 files. These opera

[PATCH] Add '--drop-all-empty-revs' to svndumpfilter include/exclude

2013-02-26 Thread vijay
Hi, Recently, I had a chance to look at a dump file with lot of empty revisions. The dump file was taken by syncing a sub-directory of a remote repository using svnsync. I decided to remove all the empty revisions from the dump file. But 'svndumpfilter include/exclude --drop-empty-revs' was o