Re: Bug Report: can't add same revision twice

This occurs when (in this case) VCP::Source::p4 tries to queue up the
a revision it's already queued up.  So the question is why it thinks it
needs to queue it up twice.  My guess is that that revision is occuring
more than once in the metadata, perhaps as branch destinations, and
that's tripping us up.

I used to have access to the Perl repository, but it lapsed a long time
ago (my p4 repository browser was mothballed when VCP started up).
Otherwise I'd run some tests here and help out.

Why do you need "--follow-branch-into"?

My first guess is that --follow-branch-into is (wrongly) causing
VCP::Source::p4 to rescan a file that was also scanned due to the source
specification.

Thanks,

Barrie