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

Question for status on accumulation of warning on svn:external instead of immediate abort

From: Achim Spangler <Achim.Spangler_at_mnet-online.de>
Date: Fri, 9 Jan 2009 10:16:04 +0100

Hi,
I registered the issue #3148 which got a reference from #3246.

When I started to dig into the problem some month ago, I detected the same
that Karl Fogel wrote in his statement at:
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=60397&orderBy=createDate&orderType=desc

"The reason I didn't commit my patch was that there was no way to
accumulate the errors and then display them as non-fatal warnings at the
end -- and I didn't have time to add the infrastructure to do that. If
we are going to alert the user, it should really be a warning, not an
error, IMHO."

And as I'm no svn internal expert, I see no near solution of this problem by
myself.

QUESTION:
Is there any plan of real svn expert developers to provide infrastructure for
collection of svn:external warnings?
- is this by any chance planned for 1.6.0?

Could an intermediate solution help, which - maybe controlled by command line
option - triggers simple ignoring of svn:external problems, and only prints
at the end "there were some ignored svn:external problem"?
--> maybe just skipping non-working entries is much easier than complete
    solution with detailed reporting

Thanks,
Achim
Received on 2009-01-09 10:16:30 CET

This is an archived mail posted to the Subversion Dev mailing list.