Re: [viewvc-users] Renamed files

"C. Michael Pilato" <[email protected]>
Newsgroups gmane.comp.version-control.cvs.viewcvs.user
Organization CollabNet, Inc.
Message-ID <4B02C146.5070205__27713.1420131356$1258471772$gmane$org@collab.net>
Gareth Dart wrote:
> Hi,
>  
> Does anyone know if there is a way to make viewvc display the current
> name for files following a cvs rename?
>  
> Executive sumnmary:  CVSNT saves filename change information in a file
> in each module folder called .directory_history so they are a property
> of the folder rather than, irritatingly, the file.  So, in your CVS
> Repository, the filename has not actually changed: CVSNT just supplies a
> renamed-on-the-fly file to CVS clients when they update/checkout/export
> and leaves the server filename as is.  Since Viewvc just looks at the
> files on the server to generate it's listings pages and seems to ignore
> the contents of .directory_history, it's still showing the old filenames
> rather than the new.
>  
> Google and Viewvc's FAQ has availed me not.  If anyone knows a way round
> this, that'd be great.

ViewVC doesn't support (or claim to support) CVSNT at this time -- only CVS
and Subversion.  We've done some simple thing to get basic handling of CVSNT
RCS trees in place, but have never even attempted something resembling
exhaustive support of that version control system.  Sorry.

-- 
C. Michael Pilato <[email protected]>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

------------------------------------------------------
http://viewvc.tigris.org/ds/viewMessage.do?dsForumId=4255&dsMessageId=2418971

To unsubscribe from this discussion, e-mail: [[email protected]].
signature.asc (application/pgp-signature, 197 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAksCwUYACgkQokEGqRcG/W4AtgCgpAXJTMzBJJpiTY/onh9/UWIq
caEAoMD2Mx9879Tb61EFzghUnlEM3RlL
=bPTh
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.