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

[Jed Brown]

Barry Smith <bsmith at mcs.anl.gov> writes:

>   Done, but note in my previous email with a full cut and paste of what I did I never got any messages about misbehavior

The following looks to me like jumbled output.

|  ~/Src/petsc  next $ git pull
|  From bitbucket.org:petsc/petsc
|   + 5fad734...6e2aac5 next       -> origin/next  (forced update)
|   * [new branch]      next-oct-2014 -> origin/next-oct-2014
|  Already up-to-date!
|  Merge made by the 'recursive' strategy.
|  ~/Src/petsc  next $

It doesn't make sense to say "Already up-to-date" and that it made a merge.
-------------- 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-users/attachments/20141002/98877a0b/attachment.pgp>