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

Re: rapidsvn feedback

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-07-30 16:30:10 CEST

"Brent R. Matzelle" <bmatzelle@yahoo.com> writes:
> Saying that the Subversion client API is a moving target would be a
> great understatement. Just yesterday RapidSVN was building fine.
> Today yet another API change surfaced that prevents a clean compile.
> I want to be up to the minute as well but without a ChangeLog of API
> changes it is difficult to keep up to date. Maybe this process can
> be improved now that clients other than svn are dependent on the API?

That's not what Ben was saying, I think. He's saying, when you *do*
commit a change, make sure it compiles against the head of Subversion
as of that moment. You don't need a ChangeLog of API changes to keep
up to date; you just need to let your compiler tell you when you're
out of date :-).

But if you did want such a log, then

   $ tools/client-side/search-svnlog.pl "subversion/include/"

would come pretty close to the desired result.

Alternatively, document the revision number of the Subversion trunk
that a given commit compiles against.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 30 16:44:43 2002

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

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