[petsc-dev] Pushing non-working code

[Sean Farley]

On Sun, Feb 3, 2013 at 11:16 AM, Matthew Knepley <knepley at gmail.com> wrote:
>
>>
>> Pushing as a checkpointing mechanism discourages review.
>
>
> Review should happend when the section is complete, but this is no way
> implies that you should not push until it is complete.

There seems to be a misunderstanding: You can push all you want … to
your own repo (we're using a DVCS for crying out loud). Rebase with
petsc-dev and then all your changesets will be grouped together and
easier to review.