From: Jarek Poplawski <jarkao2@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: netdev@vger.kernel.org, joonwpark81@gmail.com,
bugme-daemon@bugzilla.kernel.org, schwab@suse.de
Subject: Re: [Bugme-new] [Bug 9816] New: cannot replace route
Date: Sat, 26 Jan 2008 13:10:26 +0100 [thread overview]
Message-ID: <20080126121026.GB2624@ami.dom.local> (raw)
In-Reply-To: <20080125192026.e667f396.akpm@linux-foundation.org>
On Fri, Jan 25, 2008 at 07:20:26PM -0800, Andrew Morton wrote:
...
> That's not a very good analogy - the source is a kernel object. A better
> example would be:
>
> linux-2.6.24-rc8:
>
> echo foo > /tmp/1
> echo bar > /tmp/2
> echo foo > /tmp/1
>
> linux-2.6.24:
>
> echo foo > /tmp/1
> echo bar > /tmp/2
> echo foo > /tmp/1
> sh: cannot write /tmp/1: Inalid argument
Probably you are right. When I have some time to build and boot 2.6.24
at last, I hope I'll find what this example is about...
> But whatever. It used to work. People's scripts will break. Regression.
Do you mean people didn't have to change their scripts before, e.g.
from linux 2.0.? Scripts are kind of programs, and both APIs and some
'undocumented' features are achanging...
Regards,
Jarek P.
Regards,
Jarek P.
prev parent reply other threads:[~2008-01-26 12:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9816-10286@http.bugzilla.kernel.org/>
2008-01-25 22:26 ` [Bugme-new] [Bug 9816] New: cannot replace route Andrew Morton
2008-01-25 23:11 ` Jarek Poplawski
2008-01-26 3:20 ` Andrew Morton
2008-01-26 5:16 ` Joonwoo Park
2008-01-26 11:40 ` Jarek Poplawski
2008-01-26 14:10 ` Jarek Poplawski
2008-01-26 14:27 ` Andreas Schwab
2008-01-26 15:19 ` Jarek Poplawski
2008-01-27 1:11 ` Jarek Poplawski
2008-01-27 7:58 ` Jarek Poplawski
2008-01-27 9:49 ` Julian Anastasov
2008-01-27 11:14 ` Jarek Poplawski
2008-01-26 14:32 ` Jarek Poplawski
2008-01-26 12:10 ` Jarek Poplawski [this message]
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=20080126121026.GB2624@ami.dom.local \
--to=jarkao2@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=joonwpark81@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=schwab@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).