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

Re: [Subclipse-users] Blame (annotate) issues in subclipse 1.4.3

From: Mark Phippard <markphip_at_gmail.com>
Date: Thu, 14 Aug 2008 15:02:12 -0400

On Thu, Aug 14, 2008 at 2:41 PM, Gene Gorokhovsky
<ggorokhovsky_at_apriori.com> wrote:
> MP> When you tested from the command line are you 100% certain you used
> the SVN 1.5.1 command line?
> Yes. Here is the output of "svn --version"
> svn, version 1.5.1 (r32289)
> compiled Jul 25 2008, 11:09:31
> MP>Is there anything about your repository history
> that could be triggering a bug? Such as the paths being moved/renamed
> during their lifetime?
> We did move paths a while back, and there were quite a few merges. The
> blame kept working fine though until we went to 1.5 client.
> After playing a bit, I was able to reproduce the issue from the command
> line. It looks like "-g" flag (use merge history) triggers the failure.
> So
> svn blame -g -r 32937 AutomaticCastingDemo_L1Test.java_at_HEAD
> failes, but
> svn blame -r 32937 AutomaticCastingDemo_L1Test.java_at_HEAD
> works as expected.
> So this is svn's fault and not subclipse-s. It would be nice if
> subclipse could fall back to ignoring merge history, but it does appear
> that this needs to be pursued with the core svn team.
> Should I still file a subclipse issue?

We actually do detect the error you get when using -g with a pre-1.5
server, and we then just re-issue the API without that option.

Mark Phippard
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-08-14 21:02:26 CEST

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