views:

65

answers:

3

Hey,

we started working with development- and featurebranches and it is actually quite useful. But, as we do most of the bug fixes in development branches it often happens, that I work on several things at a time, waiting for them to be reviewed by our QA. Now I fear that I will forget to merge a changeset/revision back into trunk after I get clearance and so a bugfix actually doesn't find its way into trunk.

Is there a way to show the changesets from one branch that haven't been merged back to another branch (trunk) yet?

Thanks.

A: 

A very basic approach is to use

svn log --verbose

on your feature as well as your development branch. If necessary you can limit the query to specified revision:

svn log --verbose -r r1:r2

The following link about svn changesets might be interesting for you as well.

zellus
+1  A: 
  • Right-click on your working copy of the trunk
  • Choose "merge" from the TSVN context menu
  • in the merge wizard, chose "range of revision"
  • for the url, enter the url of your branch
  • click the "show log" button
  • in the log dialog, check the checkbox "include merged revisions".

Now, that log dialog (started from the merge dialog) will show you all revisions that have already been merged from the branch into trunk in gray and with an additional icon. All revisions that are shown black were not merged yet from the branch into trunk.

Stefan
Okay, "retrieval of mergeinfo unsupported" hints that we use a stone age SVN version around here. Will get it updated and try again.
Jan P.
Update done, works perfectly. "Include merged revisions" even isn't necessary, as it only shows the revisions that were merged in this commit - and as this is my dev branch there are no merges into it that are relevant to merge down.
Jan P.
A: 

We spun a service that uses the mergeinfo metadata to create a webpage that displays this information. So we now setup our "merge paths" in a configuration file (including to trunk) and this service looks for outstanding revisions that have not been merged along the merge paths.

It is VERY useful.

Dan