First time here? Check out the FAQ!

Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

answered Aug 6 '13

berak gravatar image
  • "Will that be fixed by the person by who is supposed to handle my pull request?"

    no, your job. but you'll probably get some suggestions

  • "do I delete my old fork ?"

    no, just fix the problem, and update your fork. the buildbot tests will be run automatically.

  • you want a separate branch for every problem you're trying to fix, look here

click to hide/show revision 2
No.2 Revision
  • "Will that be fixed by the person by who is supposed to handle my pull request?"

    no, your job. but you'll probably get some suggestions

  • "do I delete my old fork ?"

    no, just fix the problem, and update your fork. fork(probably with -f option). the buildbot tests will be run automatically.

  • you want a separate branch for every problem you're trying to fix, look here

click to hide/show revision 3
No.3 Revision
  • "Will that be fixed by the person by who is supposed to handle my pull request?"

    no, your job. but you'll probably get some suggestions

  • "do I delete my old fork ?"

    oh no, just doing so will destry all the history with it.just fix the problem, and update your fork(probably with -f option). the buildbot tests will be run automatically.

  • you want a separate branch for every problem you're trying to fix, look here

click to hide/show revision 4
No.4 Revision
  • "Will that be fixed by the person by who is supposed to handle my pull request?"

    no, your job. but you'll probably get some suggestions

  • "do I delete my old fork ?"

    oh no, doing so will destry destroy all the history with it.just fix the problem, and update your fork(probably with -f option). the buildbot tests will be run automatically.

  • you want a separate branch for every problem you're trying to fix, look here