On 14/11/17 13:56, Satish Balay wrote:
Unwind is a reset to next the status of master (wrt commits)
git checkout next
git reset --hard origin/master
i.e Brances that are ready for 'next' testing have to be merged into next again.
I've fixed issues for some branches - [they are clean in a
On Tue, 14 Nov 2017, Adrian Croucher wrote:
> > Petsc 'next' branch users,
> >
> > I've recreated 'next' branch - and have a backup for current 'next' at
> > next-nov-2017
> >
> > [This is eliminate some binary files - that got inadvertently
> > added. next-nov-2017 will be deleted at a later
Petsc 'next' branch users,
I've recreated 'next' branch - and have a backup for current 'next' at
next-nov-2017
[This is eliminate some binary files - that got inadvertently
added. next-nov-2017 will be deleted at a later time]
So (next branch users) please do the following (in all your git
On 11/11/17 11:47 AM, Jed Brown wrote:
The way I see it - a broken next [where folks can't easily figure out
who or which commit is responsible for the brakages] - doesn't help
much..
The fundamental problem here is that we aren't accurate enough at
placing blame and getting the appropriate
