Volker Vosskaemper wrote:
> Hello Ben,
>
> thanx for your answer. But this is more bad than that what I have now :-)
>
>> Interesting suggestion... have you tried running "svn log -v -rX"? It
>> shows a plain list of changed files. If you add the --xml switch, you
>> could even write a script that runs over a range of revnums, parses out
>> the changed paths, and combines them into a unique list.
>
> svn log -v not only gives the same unwanted flags at the beginning of the
> line additional there are the logmessages and it is possible to get an
> duplicated filename if you compare more than one rev eg. -r102:208 :-( >
> I don't want to parse that output (that's what I'm doing now :-) )
>
> For platform independent public projekts it is not nice to need unknown
> foraign helper programs, like my java parser I have written for the merge
> --dry-run output :-)
>
> I think, the information I want is already there. But packed with
> additional, for me unneeded, information. I belive that it would be only
> a few lines to code that, and I hope, that you belive, that this could be
> interesting for the public :-)
>
> The need is: plain file output (full path, as is now) and suppressing of
> lines like skipping.... etc.
>
> Again:
> This is very usefull if you want create a patchset - a list of changed
> files to update something, maybe a website, where you don't want to
> upload all the images and other files, just the new and changed :-)
>
> And if you may change this, apache ant can do all the rest of that work.
> :-)
>
> regards
>
> Volker
Perhaps you can use the language bindings for java, since you're already
talking about writing a custom parser in it. You'd be much better off
getting the raw data than the text output, at least.
Philip Miller
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 22 05:38:53 2004