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

Re: Subversion problem/feature request

From: Kevin Grover <kogrover_at_yahoo.com>
Date: 2006-07-12 03:40:23 CEST

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?
Received on Wed Jul 12 03:41:27 2006

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.