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

[Enhancement request] Ability to merge patches with developer filter

From: Ross Golder <ross_at_golder.org>
Date: 2005-11-14 04:54:05 CET

For example, I am releasing *some* code from our project's trunk branch
to a live branch. There are two developers, me and Mr X. Mr X has made
lots of changes and all are tested and ready to go live. I have been
made some drastic modifications but haven't been able to test them fully
yet. Our manager wants Mr X's code released now, but I want to exclude
my code from the release (for safety).

I have 'svn copy'ed the previous live branch to a new one, and used 'svn
merge' to merge in all the changes to trunk since the last release was
cut (from trunk), so I have a base to apply the relevant patches.

My feature request is for a kind of 'filter' that, at this point, would
allow me to only merge patches in the given range that were applied by a
given developer, or (for larger projects, perhaps with a rogue
developer), the ability to exclude patches from a certain developer
(both ways would work equally well in my two-developer case!).

As it happens, in this case, I have just merged all the changes to trunk
since the last release, and reverted the ones I made before the commit.
But, if we had both been working on the same files that wouldn't be
possible, and I'd have need to manually work out which patch
numbers/ranges in the range were Mr X's and apply them by hand with
multiple 'svn merge's.

Just a thought ;)

--
Ross
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 14 11:04:47 2005

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.