Re: [viewvc-users] viewvc and mimicing svn log "use merge history"

"C. Michael Pilato" <[email protected]>
Newsgroups gmane.comp.version-control.cvs.viewcvs.user
Organization CollabNet, Inc.
Message-ID <[email protected]>
John Tseng wrote:
> Hi all,
> 
> We recently started to do branching and merging in subversion.
> We noticed that ViewVC's "Revision log" does not show  (or have an
> option to show) the full merge history.
> 
> For the "svn log" command, we typically add the --use-merge-history (-g)
> to do this.
> 
> Is there a way to configure Viewvc to mimic the behavior of  "svn log
> --merge history" ?

ViewVC has not grown an option to support the use of merge history logic in
Subversion, and doing so is probably not simply a matter of tweaking that
boolean flag.  The Subversion API, when that flag is set, drives the log
receiver callbacks differently and in a way that ViewVC is not currently
written to expect.  Also, ViewVC would need some additional work in the UI
area to determine how to best display this (now-hierarchical) new
information.  Finally, there is (in my experience, at least) a
non-negligible performance penalty involved in employing in the
use-merge-history functionality that most admins would probably not want
their users to bear all the time.

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

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

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)

iEYEARECAAYFAkv9WMoACgkQokEGqRcG/W5TFACfV4dd2YPP7uyPWreFi5BD0tFq
4/QAnRiM1UXgHhmdB1mNt79EqqIvbnxP
=/xiP
-----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.