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

finding which branches contain a bug

From: Bart Robinson <lomew_at_pobox.com>
Date: 2006-01-04 03:21:32 CET

I have a question for how to determine which branches contain a
particular bug.

Let's say I find a bug (in one file) in trunk and want to know
what branches also have the bug. In CVS I can do annotate on
the file, find that it went in on revision 1.4, then do stat -v
on that file to see which branches/tags were made after 1.4
(e.g., 1.4.x.y, 1.77.z.w, etc).

If I do svn ls -v on http://host/repos/proj/branches I see the
branch names and a revision, but the revision is when the last
change went in on that branch, not the root of the branch. If I
could get the revision where each branch was created, I could
sort that and figure out which branches are relevant.

Is there an easier way than taking the last rev from "svn log
--stop-on-copy" for each branch? (Since that info is pretty
much static, I guess I could do it once and then maintain it in
some file via a post-commit hook.)

-- bart

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 4 03:24:10 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.