[petsc-dev] bitbucket giving wrong information

Patrick Sanan patrick.sanan at gmail.com
Wed Dec 3 22:43:32 CST 2014

Whoops, guess that wasn't the cause then!

Actually, looking at bitbucket, it looks like the PR is coming from a 
different repository (https://bitbucket.org/iaannn/petsc/).

This worked on my machine:
[petsc (master=)]$ git remote add iaannn git at bitbucket.org:iaannn/petsc.git
[petsc (master=)]$ git fetch iaannn
[petsc (master=)]$ git checkout -b 
[petsc (ianwilliamson/fix-matlab-write-bin-complex=)]$

On 04/12/14 12:57 PM, Barry Smith wrote:
> $ git checkout -b ianwilliamson/fix-matlab-write-bin-complex  origin/ianwilliamson/fix-matlab-write-bin-complex
> fatal: Cannot update paths and switch to branch 'ianwilliamson/fix-matlab-write-bin-complex' at the same time.
> Did you intend to checkout 'origin/ianwilliamson/fix-matlab-write-bin-complex' which can not be resolved as commit?
>> On Dec 3, 2014, at 9:54 PM, Patrick Sanan <patrick.sanan at gmail.com> wrote:
>> Is it possible that you have a second remote with a branch with the same name? In that case, perhaps something like:
>> git checkout -b ianwilliamson/fix-matlab-write-bin-complex  origin/ianwilliamson/fix-matlab-write-bin-complex
>> On 04/12/14 12:37 PM, Barry Smith wrote:
>>>    So some guy posts a pull request. I, in trying to follow PETSc-rules, want to check out his branch and then merge that rather than use the merge directly from the bitbucket website. So I go to the branch in the bitbucket website and bitbucket claims I can look at it with
>>> git fetch && git checkout ianwilliamson/fix-matlab-write-bin-complex
>>> (see attachment). I try that and of course it does not work:
>>> $ git fetch && git checkout ianwilliamson/fix-matlab-write-bin-complex
>>> remote: Counting objects: 56, done.
>>> remote: Compressing objects: 100% (56/56), done.
>>> remote: Total 56 (delta 48), reused 0 (delta 0)
>>> Unpacking objects: 100% (56/56), done.
>>>  From bitbucket.org:petsc/petsc
>>>     f685883..cf8fc5e  master     -> origin/master
>>>     7cadcfe..39ea070  knepley/fix-plex-orient -> origin/knepley/fix-plex-orient
>>>     565f831..ce993ff  knepley/pylith -> origin/knepley/pylith
>>>   + 3f11d05...21345e8 mlange/refactor-plex-distribute -> origin/mlange/refactor-plex-distribute  (forced update)
>>>     e9d5acc..916966e  next       -> origin/next
>>> error: pathspec 'ianwilliamson/fix-matlab-write-bin-complex' did not match any file(s) known to git.
>>> So is bitbucket lying to me or am I doing something wrong. Should this be a feature request to bitbucket ?  Remember I am living in the world where I cannot remember how to do anything and thus expect my tools to tell me how to do something. So why cannot bitbucket tell me the truth of how to get this branch?
>>>    Barry
>>> <Mail Attachment.png>

More information about the petsc-dev mailing list