A dynamic view in Clearcase should be able to access any arbitrary
file or revision associated with the VOB via the MVFS extended path
notation. So, even if you use a path name that does not exist in your
working copy due to your current config spec, you should still be able
to access deletefile@@/branch/5, for example. You should be able to
test this out directly at the command line. The dynamic view on the
server is just a vehicle to access the Clearcase database. It doesn't
matter at all what state it is in. If you think this isn't true, then
we need to understand why and evaluate other options.
On Jul 22, 4:27 am, Igor <xrevol...@gmail.com> wrote:
> On Jul 18, 7:25 pm, Jan Koprowski <jan.koprow...@gmail.com> wrote:
> > On Sun, Jul 18, 2010 at 5:39 PM, Igor <xrevol...@gmail.com> wrote:
> > > Hi,
> > > I have same ClearCase setup as described in patch of Jan Koprowski -
> > >http://reviews.reviewboard.org/r/1505/.
> > > Correct me if I wrong, in this patch each repository represents
> > > clearcase view of specific user (repository_url as defined in Jan's
> > > patch ) under /view/$user_$module_$branch.
> > This /view/$user_$module_$branch model looks like misunderstanding.
> > View for Review Board is another, different dynamic view distinct from
> > others - central view where all branches of all users are present. You
> > can get to files on this branches using extended path
> > /path/to/file@@/main/branch/version. I don't understand why branches
> > in Your model is different views - not standard ClearCase branch.
> OK. I need to fetch original file from central repository. What if
> file was removed from repository on some later stage?
> Do I need to save baseline of original file?
> BTW we use UCM ClearCase
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at