[Paraview-developers] [EXTERNAL] Re: Dashboard question

[Marcus D. Hanwell]

I am totally with you Ken, and think this is part of the power of git
and feature branches. I want to see the rabbit holes you went down. I
do clean up some of my local commits to remove the "checkpointed
broken state before leaving for the day", and rebase a little in an
attempt to appear cleverer than I am before publishing a branch but I
refrain from simply squashing it into a huge commit with a "I just
came up with this in 10 minutes, simple implementation solving all of
our problems"...

In VTK (and ITK) we have topic branch testing on Gerrit, this allows
for a topic to be built on Windows, Mac and Linux before being merged
into anything. Rebasing a really old branch can help there as the
CDash at Home builds are incremental and an old base will case a full
rebuild. The Change-Ids can then link back to the code review and test
build submissions too.

On Fri, Mar 2, 2012 at 10:26 AM, Moreland, Kenneth <kmorel at sandia.gov> wrote:
> SUCCESS! Rebasing gives huge monolithic commits with overly-simple
> explanations that explain nothing after you're dead and gone.  Topic
> branches collect your hundreds of commits into a narrative describing all
> the challenges you faced and design decisions you implemented.  I love
> having lots of commits so when I go back and say "why did I write that
> crazy-ass piece of code?" I can do a git blame and find the commit
> describing the obscure but important corner case said code correctly
> handles.
>
>
> Perhaps we can just agree to disagree =]
>
> -Ken
>
> On 3/2/12 8:13 AM, "Biddiscombe, John A." <biddisco at cscs.ch> wrote:
>
>>PS. Ken. FAIL! Rebasing is very sexy and I like it lots. I can take
>>months of rubbish coding and turn it into a nice clean commit with a
>>simple explanation instead of hundreds of hard to unravel mini-mistakes.
>>After I'm dead and gone, people with truly think that I never made any
>>coding mistakes :)
>
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers