On Fri, Oct 06, 2006 at 07:57:32AM +0200, Jarek Poplawski wrote:
On Thu, Oct 05, 2006 at 01:52:19PM -0700, Randy Dunlap wrote:
On Thu, 14 Sep 2006 10:29:30 +0200 Jarek Poplawski wrote:
On Thu, Sep 14, 2006 at 10:25:32AM +0200, Jarek Poplawski wrote:
...
Mozilla Firefox is breaking all
On Fri, Oct 06, 2006 at 07:57:32AM +0200, Jarek Poplawski wrote:
On Thu, Oct 05, 2006 at 01:52:19PM -0700, Randy Dunlap wrote:
...
see http://mbligh.org/linuxdocs/Email/Clients/Thunderbird
...
dangerous feature of Thunderbird - you never could be sure
how a message will look because it is
On Thu, 14 Sep 2006 10:29:30 +0200 Jarek Poplawski wrote:
On Thu, Sep 14, 2006 at 10:25:32AM +0200, Jarek Poplawski wrote:
...
Attachments are discouraged, but some corporate mail systems
provide no other way to send patches.
I thought they didn't read this but now I understand for
On Thu, Oct 05, 2006 at 01:52:19PM -0700, Randy Dunlap wrote:
On Thu, 14 Sep 2006 10:29:30 +0200 Jarek Poplawski wrote:
On Thu, Sep 14, 2006 at 10:25:32AM +0200, Jarek Poplawski wrote:
...
Attachments are discouraged, but some corporate mail systems
provide no other way to send
On 12-09-2006 00:04, Jeff Garzik wrote:
John W. Linville wrote:
...
Not too explicitly, but I think Andrew mentions it in The Perfect
Patch:
http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt
While you are looking, you might review Jeff's version of the same idea:
On Thu, Sep 14, 2006 at 10:25:32AM +0200, Jarek Poplawski wrote:
...
Attachments are discouraged, but some corporate mail systems
provide no other way to send patches.
I thought they didn't read this but now I understand for whom
Mozilla Firefox is breaking all those lines with no mercy!
On Sat, Sep 09, 2006 at 11:04:59AM -0500, Larry Finger wrote:
John W. Linville wrote:
On Fri, Sep 08, 2006 at 08:47:54PM -0500, Larry Finger wrote:
PLease send this upstream for inclusion in 2.6.18, if possible. This
patch will not work for
wireless-2.6. That patch will be sent to you
John W. Linville wrote:
On Sat, Sep 09, 2006 at 11:04:59AM -0500, Larry Finger wrote:
John W. Linville wrote:
OK, I see now. The patch won't apply to the upstream branch at all
due to the open-coded locking patch applied previously.
The problem now is that if I send this up for 2.6.18 then
On Mon, Sep 11, 2006 at 02:59:01PM -0500, Larry Finger wrote:
John W. Linville wrote:
Also, if you could just use --- instead of a long line of ==,
I think I would have to do less manual processing...thanks!
Sorry about the === rather than ---. Is that documented somewhere?
Not too
John W. Linville wrote:
On Mon, Sep 11, 2006 at 02:59:01PM -0500, Larry Finger wrote:
John W. Linville wrote:
Also, if you could just use --- instead of a long line of ==,
I think I would have to do less manual processing...thanks!
Sorry about the === rather than ---. Is that documented
On Fri, Sep 08, 2006 at 08:47:54PM -0500, Larry Finger wrote:
PLease send this upstream for inclusion in 2.6.18, if possible. This patch
will not work for
wireless-2.6. That patch will be sent to you soon.
Are you saying this will break the upstream branch of wireless-2.6?
I'm not too
John W. Linville wrote:
On Fri, Sep 08, 2006 at 08:47:54PM -0500, Larry Finger wrote:
PLease send this upstream for inclusion in 2.6.18, if possible. This patch
will not work for
wireless-2.6. That patch will be sent to you soon.
Are you saying this will break the upstream branch of
John,
Larry Finger wrote:
I would like to get a listing of patches for bcm43xx-softmac that are
queued but not yet applied, and the order in which they will be applied.
I want to make sure nothing has fallen through the cracks, and that the
patches will apply cleanly.
I know you have
John,
PLease send this upstream for inclusion in 2.6.18, if possible. This patch will
not work for
wireless-2.6. That patch will be sent to you soon.
Larry
=
This patch fixes a bug in the bcm43xx driver in 2.6.18-rcX that hangs the
machine due to
14 matches
Mail list logo
