[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] Commit dialog - text vs property changes

From: Mark Phippard <markphip_at_gmail.com>
Date: Thu, 30 Sep 2010 11:23:44 -0400

On Wed, Sep 29, 2010 at 10:03 PM, Shaun Pinney
<shaun.pinney_at_bil.konicaminolta.us> wrote:

> Thanks for describing the decorators (I'm new to Subclipse) - I think they
> get us very close to what we're looking for.  It would be great if there
> was also a decorator for 'svn:mergeinfo changed' - or possibly some other
> indication aside from a decorator.  This way, we could easily know which
> changes were to 'svn:mergeinfo only' and we could skip them during pre-commit
> reviews.  It would save us some time after merges.  Do you think this could
> be added?

What do you mean by pre-commit reviews? Maybe you should use create
patch? That shows the property changes in the content and might make
it easier to sift through.

I saw your post on the SVN users@ list and while I did not read it
carefully, you are not experiencing anything that most other merge
tracking users have not reported. You have to (or at least should)
commit these mergeinfo changes with the content. SVN 1.7 is going to
reduce the noise. In 1.6, the only way to reduce it is to eliminate
nodes that have mergeinfo and try to get it consolidated at your
project root. Then encourage users to do all merges and commits from
the project root so that it does not come back.

Mark Phippard
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2010-09-30 17:23:55 CEST

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.