* Johann Oskarsson <Johann> writes:
> Steve Youngs <steve@xxxxxxxxxxx> writes:
>> As I mentioned in my build report... SXEmacs is dumping core in X.
>> This has no doubt been introduced by some breakage in my
>> mega-indentatin patch.
I really don't understand what happened, but I have fixed it by...
- reverting the indentation on input-method-xlib.c
- re-re-indent input-method-xlib.c in XE by:
C-x h
C-M-\
I'll commit this re-re-re-indented version in a moment.
>> From irc:
> <myrkraverk> I'm tired,and hungry, and I've no idea, except it looks like a
> problem in input-method-xlib.c:679 or input-method-xlib.c:630
[06:51]
I had a look, but nothing screamed "peek-a-boo I'm your bug" at me.
> <myrkraverk> (I assume you can read C, if not write it)
On a good day, with a tail wind, I can do both (in a fairly limited
kinda way, but every day I get better and better).
> Now I'm going to go get some breakfast, then I'm going to sleep some,
> and if no one has fixed it when I wake up, I'll see if I can spare
> some time.
Thanks, but I seemed to have fluked it this time. :-)
> Steve: Please comment on this responce regarding your support
> policy and general QA (Quality Assurance).
My policy is that it is OK to break things. OK, providing you make
steps to fix the problem ASAP. My repo won't always run or even
build, and I am totally cool with that.
What I wouldn't be cool with is merging in somebody's broken code and
that person not being prepared to even try to fix it.
In the example we have just seen with yours truly breaking things. I
sent a report to the list immediately in the hope that someone far
more knowledgeable than myself could shed some light. You (Johann)
replied, giving me enough information to be able to fix the problem.
If no such response was forthcoming I would have reverted the
indentation patch without hesitation.
Rest assured that any tarball release that I make will both build and
run in several configurations on my box here before I release. And
the test suite will pass all tests 100%.
> Oh, and about QA, should we adjust the OOo QA strategy?
What does "OOo" mean?
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| In space, |
| No one can hear you rip a stinky |
|------------------------------------<steve@xxxxxxxxxxx>---|
pgpXxuK6f4ODa.pgp
Description: PGP signature
|