[petsc-dev] bitbucket giving wrong information

[Satish Balay]

On Thu, 4 Dec 2014, Barry Smith wrote:

> 
> > On Dec 4, 2014, at 3:33 PM, Jed Brown <jed at jedbrown.org> wrote:
> > 
> > Patrick Sanan <patrick.sanan at gmail.com> writes:
> >>> Sure thanks, but there is no way I can remember this; hence bitbucket should walk me through it.
> >> Yeah - their helpful hint doesnt work when pulling across repos, which is a useful, probably typical, case, so it'd be better for then to have said nothing!
> > 
> > GitHub does better here:
> > 
> > | You can merge this Pull Request by running:
> > | 
> > |   git pull https://github.com/someuser/petsc someuser/branch-name
> 
>   Nice, this is what I want. Has bitbucket been made aware of their definiciecy so they can fix it?

I think we need a workflow where we create a localbranch for each of
these pull requests - not directly merge (in case we need to make
local fixes).

I see some such branches currently used..

$ git branch -r |grep pull
  origin/dmeiser/pullrequest-fix-PetscOptionsEnum
  origin/dmeiser/pullrequest-fix-PetscOptionsEnum2
  origin/dmeiser/pullrequest-fix-cusp-bjacobi2
  origin/dmeiser/pullrequest-fix-dmda-cusparse
  origin/dmeiser/pullrequest-fix-format-specifier-ex43
  origin/dmeiser/pullrequest-remove-thrust-py


Satish