Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

How to patch

0 views
Skip to first unread message

Mike Easter

unread,
Feb 7, 2010, 1:27:44 PM2/7/10
to
Treat me gently, please; I'm a total newb at this :-)

I'm an advocate of format=flowed. In my linux tbirds, I use 2.0.0.23
which f=f is OK.

The tbirds3 upto and including 3.1a1 are all b0rken in the f=f condition
because when posting they all strip trailing spaces from previous
citations in news messages.

There are a number of bug reports on this issue, which tend to reduce by
eliminating similars into the common one
https://bugzilla.mozilla.org/show_bug.cgi?id=456053

That bug has a patch posted. patch1.0 (1.46 KB, patch) 2008-09-22 00:55
PDT, Andriy Tkachuk - Index: content/base/src/nsPlainTextSerializer.cpp

I don't know the first thing about patching, except to assume that one
takes the source code and does something to patch it and then recompiles it.

I've seen some moz wiki pages on hacking, but they don't tell me what I
need to know to use the specific patch cited above.

Alternatively, I could just uninstall the tbirds 3.0.1 and 3.1a1 that I
have on the XP systems I run and install 2.0.0.23 in their place; but I
would like to try to patch the XP versions for the experience of doing it.

--
Mike Easter

Nikolay Shopik

unread,
Feb 7, 2010, 2:03:02 PM2/7/10
to
That patch need owner it's kinda outdated, therefore its need little
rework to allow patch current code and compile it.

Mike Easter

unread,
Feb 7, 2010, 3:24:22 PM2/7/10
to
Nikolay Shopik wrote:
> On 07.02.2010 21:27, Mike Easter wrote:

>> I'm an advocate of format=flowed. In my linux tbirds, I use 2.0.0.23
>> which f=f is OK.
>>
>> The tbirds3 upto and including 3.1a1 are all b0rken in the f=f condition
>> because when posting they all strip trailing spaces from previous
>> citations in news messages.

>> That bug has a patch posted.

>> Alternatively, I could just uninstall the tbirds 3.0.1 and 3.1a1 that I


>> have on the XP systems I run and install 2.0.0.23 in their place

> That patch need owner it's kinda outdated, therefore its need little


> rework to allow patch current code and compile it.

Thanks for the reply.

All things considered, mainly the disadvantages of what is broken in
Tbird3 contrasted with what isn't right about Tbird2, I think I had best
just go back to Tbird 2.0.0.23 and work around its problems.

I'm not a developer, but it seems that 3 was released with significant
regressions compared to 2. To me, that is a beta 3, but then/instead
that beta3 was allowed to start a 6 month clock based on an unfinished
release which accelerates the death or abandonment of support for 2
because it costs scant resources which are needed to shape up 3.

That surely can't be the standard model for development - incomplete
versions phasing out versions which are better in some ways based on a
fast release clock. I don't think tbird's bugfree development is
proceeding so smoothly as to have such a fast end of life clock.


--
Mike Easter

0 new messages