[vtk-developers] ANN: All VTK commits through the topic stage

Aashish Chaudhary aashish.chaudhary at kitware.com
Thu Oct 14 14:49:57 EDT 2010


>
>
> If you do not want to merge it/you no longer wish to share it.
>
>>
>>> Is there are branch naming convention?  I tend to use
>>> lowercase-words-with-dashes.
>>>
>>
> We have asked that they be meaningful, but we are not enforcing any
> particular naming convention. Perhaps we should adopt a default style, and
> lower case with dashes seems reasonable.
>
>>
>>> I was about to ask the same as well. Also I am assuming that  with this
>> change updating the submodule references need staging too (thats what I have
>> been doing)
>>
>
> Well...VTK doesn't have any submodules. I assume you are referring to
> ParaView now? The submodule update commit should ideally be the only thing
> in that particular commit, and it should point to a VTK master (or other
> submodule) that has been merged. This should be staged along with the rest
> of the topic branch.
>
>>
>> Sorry, yes I was referring to ParaView.


> One thought that in future we might end with 1000 or more branches, do we
>> have a policy for clean up or thats work in progress?
>>
>
> When you merge a topic into all integration branches (currently just
> master) then the topic is automatically deleted from the stage. If you do
> a,
>
Great. I guess then the ones that are not merged will be deleted at some
point?

git fetch stage --prune
>

Yes this was helpful.  I have been doing this.

Thanks,



-- 
| Aashish Chaudhary
| R&D Engineer
| Kitware Inc.
| www.kitware.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20101014/62ad44c5/attachment.html>


More information about the vtk-developers mailing list