On Wed, 20 Sep 2006, Rich Williams wrote: ... > There are a few other things we'd like to add ... > > - somewhere to store some defaults (we always use -b, but if you forget, > you can sometimes get confusing results).
+1. I like the idea of a ~/.subversion/svnmerge-config file. > - a way to limit the considered revisions to a single author (i.e. show me > which of my changes are on trunk, but not on the release branch) Is this a common use case? > - a way of suppressing the revisions which are just setting up branches > (i.e. Initialized merge tracking via svnmerge). Specifically, supressing revisions which initialize merge tracking meta data via svnmerge sounds reasonable. What other cases were you thinking of?
pgpf5yXTZR6OC.pgp
Description: PGP signature
_______________________________________________ Svnmerge mailing list [email protected] http://www.orcaware.com/mailman/listinfo/svnmerge
