[petsc-dev] Pushing non-working code

[Matthew Knepley]

On Sun, Feb 3, 2013 at 12:27 PM, Sean Farley <sean at mcs.anl.gov> wrote:

> 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.
>

I do not misunderstand you Sean.

   Matt

-- 
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130203/7bc2f768/attachment.html>