Login | Register
My pages Projects Community openCollabNet

Discussions > dev > Re: [Subclipse-dev] subclipse 1.7: why is it then now merge->block revision seems to need to download the whole revision?

subclipse
Discussion topic

There will be a brief maintenance window every Friday at 17:00 Pacific.
For further details, see CollabNet's maintenance and upgrade policy.

Back to topic list

Re: [Subclipse-dev] subclipse 1.7: why is it then now merge->block revision seems to need to download the whole revision?

Author jcompagner
Full name jcompagner
Date 2011-08-16 07:16:52 PDT
Message ahh ok then that's what i am seeing now.
A bit annoying because many times when i do block version it is
because that was a big binary dump (an eclipse target or plugins that
we compile against) on a branch that i don't need on trunk. (or
another branch)
But i was correct in seeing that it now takes way more time to do it
with those kind of commits.
I can live with it, (just need to be sure that i am at home or at a
place with a fast Internet connection :) )

The other new feature "Reduced subtree mergeinfo changes" is paying
back the lost time big time..
I still have a few co workers that sometimes do merge on file only,
instead of root. Even after i told them quite a few times how to do
it!!
so how many times i also have deleted the svn:merge property on
specific files or dirs.... and committed that with a merge from my
self, i lost count..
But i guess that should be all over now!

johan


On Tue, Aug 16, 2011 at 16:07, Mark Phippard <markphip at gmail dot com> wrote:
> On Tue, Aug 16, 2011 at 9:57 AM, jcompagner <jcompagner at gmail dot com> wrote:
>>
>> Was that also in 1.6? I can't remember that
>>
>> But now if i do block revision of a quite a large commit it has to
>> download many megabytes of that commit first.
>> Why is that? Can't it just add that revision it to the properties??
>> Because thats the only thing it is really changed
>>
>
> I assume you know it is the Subversion code doing this, so nothing we can do
> about it regardless.
> There were changes in --record-only merges made in 1.7:
> http://subversion.ap​ache.org/docs/releas​e-notes/1.7.html#mer​ge-tracking-enhancem​ents
> I believe that --record-only used to only record the revision you were
> recording.  Now it also looks if that revision did any merges and also
> applies the mergeinfo from that revision.  So that must be the traffic you
> are seeing.  See:
> http://svn.haxx.se/d​ev/archive-2009-09/0​520.shtml
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
>

« Previous message in topic | 3 of 4 | Next message in topic »

Messages

Show all messages in topic

Subject
Author
Full name
Date posted
+
[Subclipse-dev] subclipse 1.7: why is it then now merge-&gt;block revision seems to need to download the whole revision? jcompagner jcompagner 2011-08-16 06:57:55 PDT
     Re: [Subclipse-dev] subclipse 1.7: why is it then now merge-&gt;block revision seems to need to download the whole revision? markphip Mark Phippard 2011-08-16 07:07:53 PDT
         Re: [Subclipse-dev] subclipse 1.7: why is it then now merge-&gt;block revision seems to need to download the whole revision? jcompagner jcompagner 2011-08-16 07:16:52 PDT
             Re: [Subclipse-dev] subclipse 1.7: why is it then now merge-&gt;block revision seems to need to download the whole revision? markphip Mark Phippard 2011-08-16 07:45:43 PDT
Messages per page: