Re: Subversion problem/feature request

To: Nico Kadel-Garcia <nkadel@comcast.net>, Filips Jeļisejevs <F.Jelisejevs@alise.lv>, users@subversion.tigris.org
From: Kevin Grover <kogrover@yahoo.com>
Date: 07/12/2006 04:40AM
Subject: Re: Subversion problem/feature request

how about
    svn log -r REV1:REV2 --verbose

And grep for the file mods.  Could also output to XML (--xml) and parse that.

----- Original Message ----
From: Nico Kadel-Garcia <nkadel@comcast.net>
To: Filips Jeļisejevs <F.Jelisejevs@alise.lv>; users@subversion.tigris.org
Sent: Monday, July 10, 2006 4:51:32 AM
Subject: Re: Subversion problem/feature request

 

----- Original Message -----

From: Filips Jeļisejevs

To: users@subversion.tigris.org

Sent: Friday, July 07, 2006 9:51 AM

Subject: Subversion problem/feature request

Hallo!

We are trying to introduce SVN in our project (large system maintenance), but stumbled into a problem.
What we need is the possibility to make weekly deliveries (versions) which would contain only those files in a project, that were changed during this week.

I tried simple approach with a svn checkout command with --revision swith passing revision range. Unfortunately I got the response that revision range is not allowed with checkout.

From documentation it is unclear whether it is a bug or intentional.
If it is intentional could someone explain, why is it so?
What could be possible workarounds for my problem?

 

Why not simply do two checkouts, and run a "rsync --dry-run --exclude .svn WC1 WC2", and use that to bundle up the difference? Or send the output of an "svn diff branch@revision1 branch@revision2" command to list and bundle the appropriate files?