[Paraview] VTK version

Marcus D. Hanwell marcus.hanwell at kitware.com
Fri Jul 9 10:27:55 EDT 2010


On Fri, Jul 9, 2010 at 4:25 AM, Michael Wild <themiwi at gmail.com> wrote:

>
> On 9. Jul, 2010, at 1:52 , François Bissey wrote:
>
> >> It is 5.6.0 + some additional patches as VTK 5.6.0 was released before
> >> ParaView 3.8.0 was finished. If you checkout the VTK release branch. The
> >> commit ParaView 3.8.0 used was:
> >>
> >> 8b2449871dca83d542cc7d8093da5fee3c70ebb1
> >>
> >> Author: Dave DeMarle <dave.demarle at kitware.com>  2010-05-19 14:25:56
> >> Committer: David Partyka <dave.partyka at kitware.com>  2010-05-21
> 08:59:24
> >> Parent: 33a0bc981c98fc81bc5351ad27ad018e9cdc6dc1 (STYLE: Remove tabs.)
> >> Child:  9fcf02d503c6fb13fa5104deb3956a77ff079a3a (COMP:
> >> SetNumberOfHistogramBins(int*) missing definition, added)
> >> Branches: release, remotes/origin/release
> >> Follows: v5.6.0
> >> Precedes:
> >>
> >>    Take timestamps of key portions of parallel rendering algorithm.
> >>
> > Is there an easy to get the diff between the released vtk-5.6.0 and
> > and the branch used in paraview-3.8.0?
> >
> > Francois
>
> Gitweb doesn't do diffing between arbitrary commits, so probably the
> easiest way is to just checkout the v3.8.0 tag from the ParaView repository,
> initialize the submodules, change into the VTK directory and do a "git diff
> v5.6.0".
>

If you have a checkout of VTK, the following would give you a diff between
the tag and the hash used in ParaView,

git diff v5.6.0..8b2449

You can also replace diff with log to see the commits, or log -p to see the
commits with diffs for each commit. I hope that help.

Thanks,

Marcus
--
Marcus D. Hanwell, Ph.D.
R&D Engineer, Kitware Inc.
(518) 881-4937
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20100709/25139b35/attachment.htm>


More information about the ParaView mailing list