From: Diego Calleja <diegocg@gmail.com>
To: Diego Calleja <diegocg@gmail.com>
Cc: paulkf@microgate.com, alan@lxorguk.ukuu.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: pppd oopses current linu's git tree on disconnect
Date: Tue, 24 Jan 2006 04:48:46 +0100 [thread overview]
Message-ID: <20060124044846.de6508eb.diegocg@gmail.com> (raw)
In-Reply-To: <20060123034243.22ba0a8f.diegocg@gmail.com>
El Mon, 23 Jan 2006 03:42:43 +0100,
Diego Calleja <diegocg@gmail.com> escribió:
> Ok - I seem to be able to reproduce it in a unpatched kernel using
> a lengthy session. I will try your patch and report back.
It doesn't seems to happen today at least, after a lentghty session
similar to the one which triggered the bug.
next prev parent reply other threads:[~2006-01-24 3:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 0:06 pppd oopses current linu's git tree on disconnect Diego Calleja
2006-01-19 17:33 ` Paul Fulghum
2006-01-19 22:07 ` Diego Calleja
2006-01-19 22:39 ` Paul Fulghum
2006-01-23 2:42 ` Diego Calleja
2006-01-24 3:48 ` Diego Calleja [this message]
2006-01-24 22:06 ` Paul Fulghum
2006-01-24 23:25 ` Alan Cox
2006-01-24 23:44 ` Paul Fulghum
2006-01-25 0:22 ` Alan Cox
2006-01-25 21:00 ` Paul Fulghum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060124044846.de6508eb.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=paulkf@microgate.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox