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

Barry Smith bsmith at mcs.anl.gov
Thu Oct 2 11:53:15 CDT 2014


  It is not jumbled output. It is the output I got

On Oct 2, 2014, at 11:47 AM, Jed Brown <jed at jedbrown.org> wrote:

> 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.



More information about the petsc-users mailing list