[petsc-dev] [petsc-users] petsc git next branch *is* unwound!

[Jed Brown]

Satish Balay <balay at mcs.anl.gov> writes:

> You would have to delete both 'next' and 'wdn_mods_next' branches from
> all your clones - and recreate them.

Do your normal "git remote update" (or git fetch) in your "master" clone
(confusing to use the same name to refer to a repository and a branch).
I'll call the repository Mirror.  Anyway, you should see that all three
branches are updated.  'maint' and 'master' should fast-forward, while
'next' will say "forced update".

After that, recreate 'next' on the clones just like in Satish's original
email.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20141002/2b091d72/attachment.sig>