[petsc-dev] candidate branches for master

[Matthew Knepley]

On Thu, Feb 27, 2014 at 10:53 AM, Satish Balay <balay at mcs.anl.gov> wrote:

> On Thu, 27 Feb 2014, Jed Brown wrote:
>
> > Satish Balay <balay at mcs.anl.gov> writes:
> >
> > > Current list of branches that are merged to next - but not yet merged
> to master.
> > >
> > > Jed, I don't see 'shri/update-SuiteSparse' in this list. Any idea why?
> >
> > The origin branch detection is messed up when a branch merges to 'next'
> > more than once.  When not dealing with 'maint', I use the much simpler
> > command:
> >
> > comm -12 <(git branch -r --merged next | sort) <(git branch -r
> --no-merged master | sort)
>
> Ok. I'll start using the alternative..
>

Did someone rewind master?

   Matt


> thanks,
> Satish
>
>


-- 
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/20140227/f14ead4a/attachment.html>