On Wed, Jul 15, 2009 at 12:30:38PM -0700, Steven Jackson wrote:
> [Background]
> Each week we release our code to our live server via a vendor branch
> that is created each week as a copy of trunk. I perform a svn diff
> between the previous release and the new release, and capture the output
> to send in an email to all our developers so that they can review all
> the changes and make sure that everything going live is supposed to.
>
> The resulting list is long and contains all diff info from all
> developers. If I could send an email containing only the diffs generated
> by each author to that author, then reviewing this list would be more
> manageable.
How meaningful is it to look at just *my* changes when there are
presumably other related changes being performed by other developers?
Surely there is a better process for verifying that "everything going
live is supposed to"? Code reviews, bug/feature tracking?
> [What I would like to do]
> Is it possible to generate a diff list per author (developer)? So, I can
> generate a svn diff, but the resulting output only contains commit info
> from a specific author?
The only thing I can think of is:
- svn log -r[this week's revisions] --xml
- parse the xml to group all of an author's changes together and
generate a list of all the revisions committed by that author
- svn diff -c[myrev1] -c[myrev2] -c...
That sounds like a lot of work for dubious gain.
Good luck,
tyler
Received on 2009-07-15 22:03:44 CEST