How I Patch Piloted lately and some tricks about merge proposals

[Stephen J. Turnbull]

Martin Pool writes:

 > Maybe you'd like to follow up with some of these people?

I don't understand the Bazaar code well enough to help people who are
already writing patches.  Blind leading the blind, and all that.

 > After some experimentation with xfail I actually don't think having
 > the test in the tree is much better than just having the bug in the
 > database, unless you're actively working on fixing it.

OK, as long as it *is* in the database.  I'm just suggesting
converting it from "patch" to "bug" (although maybe I lost context and
these are the "bug-with-patch" issues you mentioned earlier? if so, my
apologies).

I know that XEmacs has had some XFAILs that have been there for years
now, and occasionally somebody (other than the usual suspects) does
step up to work on one.  It depends on how hard it is to write the
test though, and it's not always easy to turn something that's trivial
to exercise interactively into an automated test.

 > If you would like to take some patches in this category from the url I
 > posted previously and turn them into xfail tests we will take those
 > patches though.

Fair enough, that would be a place to start on the code study too, I
guess.  Not going to happen before late March, though.  I just got
kicked out of one of my rooms with 2 days' notice, it's moving week
(with finals etc impending...).