1. 08 Apr, 2015 1 commit
    • Brad King's avatar
      Documentation: Update required Git version to 1.7.2 · ab5456f4
      Brad King authored
      Our 'git-gitlab-push' script requires Git 1.7.2 or greater to use the
      'git -c <name>=<value> ...' configuration option.  Since 1.7.2 came out
      in 2010 it is reasonable to expect developers to have it in 2015.
  2. 01 Apr, 2015 2 commits
  3. 31 Mar, 2015 1 commit
    • Dan Lipsa's avatar
      Redesign "vtkGhostLevels" arrays and related ghost functionalties. · 4dee0274
      Dan Lipsa authored
      Co-authored-by: default avatarYuanxin Liu <leo.liu@kitware.com>
      Co-authored-by: Berk Geveci's avatarBerk Geveci <berk.geveci@kitware.com>
       -The semantics of each unsigned char in the ghost arrays changes:
        Instead of storing a numeric value representing how far a cell is
        from the boundary, it is now a bit field specified by
        vtkDataSetAttributes::CellGhostTypes and
        vtkDataSetAttributes::PointGhostTypes.  The bit field is consistent
        with VisIt specs.
      - Previously, filters strip all ghost cells they request from upstream
        before finalizing the output. This is no longer done.
      - vtkUniform grids previously supported blanking through member arrays
        vtkUniformGrid::CellVisibility and
        vtkUniformGrid::PointVisibility. These arrays are removed and the
        blanking functionality are supported through the new ghost arrays
      - the "vtkGhostLevel" arrays for cell and point data are renamed to
        vtkDataSetAttributes::GhostArrayName() ("vtkGhostType").
      - the version for VTK Legacy files is increased to 4.0 and the version for
        VTK XML files is increased to 2.0. When reading older files we
        convert vtkGhostLevels array to vtkGhostType.
  4. 19 Mar, 2015 1 commit
  5. 18 Mar, 2015 1 commit
  6. 17 Mar, 2015 3 commits
    • Ben Boeckel's avatar
      docs: add buildbot information · 4265bc0e
      Ben Boeckel authored
    • Brad King's avatar
      Documentation: Add links to GitLab markdown documentation · 0bd3fbdb
      Brad King authored
      The "Review a Merge Request" section primarily depends on comments made
      in GitLab.  Link from this section to the GitLab markdown documentation.
      In particular, the special reference syntax options will be very
    • Brad King's avatar
      Documentation: Revise Merge Request creation instructions · 2f89fb53
      Brad King authored
      Move use of the "Submit merge request" button to the last step.  Add a
      step for the "Title" field before the "Description" field.  In the
      "Description" field, split various hints into bullet points to make them
      more distinct.  Provide a complete example of a description.  Explicitly
      state that the other fields may be left blank.
      Also mention in the "Review a Merge Request" section that "@" syntax
      presents completion.  It is better to use completion there than in the
      Description field because it will complete developers with access to
      the target repository instead of just the source repository.
      Inspired-by: Ben Boeckel's avatarBen Boeckel <ben.boeckel@kitware.com>
  7. 16 Mar, 2015 1 commit