[vtk-developers] [VTK 0014170]: Segfault in vtkSmartVolumeMapper

[Biddiscombe, John A.]

In the old days, when I found a silly bug that needed fixing, I committed it to the repository.

Now It seems I have to 
1) file a bug report (for something so trivial the bug report takes longer then the fix)
2) attach the patch to the bug report 
3) create a topic branch (done topic_0014170, from VTK master)
4) push a branch to gerrit (ok...)
But that doesn't work because it tells me that I need " [remote rejected] (missing Change-Id in commit message)" - I've run all the setup-development scripts and I'm sure this stuff used to work. (And where did all the stage branches go?) Am I supposed to just make up an Id or do I get one from somewhere?
Anyway ... After I fix that, I then have to ask people to review it (a waste of their time unfortunately since it's such a simple fix - and clearly whoever submitted this code originally didn't get it reviewed because it was utter nonsense) ... and then presumably wait around for it to make it eventually into a paraview branch.

Is there not an easier way than this. It pains me that I've basically given up making contributions to vtk/paraview because it is much easier to just keep fixes in my own branch and save myself the trouble. 

JB


> -----Original Message-----
> From: vtk-developers-bounces at vtk.org [mailto:vtk-developers-
> bounces at vtk.org] On Behalf Of Mantis Bug Tracker
> Sent: 15 July 2013 12:47
> To: vtk-developers at vtk.org
> Subject: [vtk-developers] [VTK 0014170]: Segfault in
> vtkSmartVolumeMapper
> 
> 
> The following issue has been SUBMITTED.
> ==========================================================
> ============
> http://paraview.org/Bug/view.php?id=14170
> ==========================================================
> ============
> Reported By:                John Biddiscombe
> Assigned To:
> ==========================================================
> ============
> Project:                    VTK
> Issue ID:                   14170
> Category:                   (No Category)
> Reproducibility:            have not tried
> Severity:                   minor
> Priority:                   normal
> Status:                     backlog
> Project:                    TBD
> Type:                       crash
> Resolution:                 open
> Fixed in Version:
> ==========================================================
> ============
> Date Submitted:             2013-07-15 06:47 EDT
> Last Modified:              2013-07-15 06:47 EDT
> ==========================================================
> ============
> Summary:                    Segfault in vtkSmartVolumeMapper
> Description:
> Bad code causes segfault. Patch attached
> ==========================================================
> ============
> 
> Issue History
> Date Modified    Username       Field                    Change
> ==========================================================
> ============
> 2013-07-15 06:47 John BiddiscombeNew Issue
> 2013-07-15 06:47 John BiddiscombeFile Added:
> 0001-Fix-a-segfault-in-setting-of-GPU-resampler-input.patch
> ==========================================================
> ============
> 
> _______________________________________________
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
> 
> Follow this link to subscribe/unsubscribe:
> http://www.vtk.org/mailman/listinfo/vtk-developers