[petsc-dev] *unwind* next branch

[Dmitry Karpeyev]

On Tue, Jun 9, 2015 at 6:06 PM Barry Smith <bsmith at mcs.anl.gov> wrote:

>
> > On Jun 9, 2015, at 5:48 PM, Satish Balay <balay at mcs.anl.gov> wrote:
> >
> > I've recreated 'next' branch - and have a backup for current 'next' at
> > '
> > The following branches need to be remerged to next.
>
>    Preferably AFTER they have been fixed to actually build cleaning with
> no errors/warnings on next including with c++, complex etc.
>
> >
> > $ comm -12 <(git branch -r --merged next-jun-2015 | sort) <(git branch
> -r --no-merged v3.6 | sort)
> >  origin/jed/assembly-perf
> >  origin/jed/mat-assembly-perf
> >  origin/jed/tao-status-string
> >  origin/pr192/Fande-Kong/scalable-matincreaseoverlap/master
>
This PR was declined.  It has been resubmitted as PR305, but it's not ready
to merge.  In particular, Fande should see if anything from pr192/xxx needs
to be merged into the new PR.


> >  origin/tisaac/knepley/feature-composable-callbacks
> >
> >
> > Satish
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20150610/0cc4ea12/attachment.html>