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

Re: How to get a plain list of changed files

From: Volker Vosskaemper <volker.vosskaemper_at_cenote.de>
Date: 2004-03-21 23:25:51 CET

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

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Mar 21 23:26:18 2004

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

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