netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: netdev@vger.kernel.org, Joonwoo Park <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 00:11:57 +0100	[thread overview]
Message-ID: <479A6CBD.4010908@gmail.com> (raw)
In-Reply-To: <20080125142603.a73fd7a2.akpm@linux-foundation.org>

Andrew Morton wrote, On 01/25/2008 11:26 PM:

>> On Fri, 25 Jan 2008 13:23:49 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
>> http://bugzilla.kernel.org/show_bug.cgi?id=9816

...

> I'd agree with Andrea: replacing a route with itself a) used to work and b)
> should still work (surely)?

...on the other hand:

$ touch file1
$ cp file1 file1
cp: `file1' and `file1' are the same file
$ mv file1 file1
mv: `file1' and `file1' are the same file

and: 'everything' in 'linux' is file...

ergo: route cannot replace with itself!

Regards,
Jarek P.

  reply	other threads:[~2008-01-25 23:09 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 [this message]
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

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=479A6CBD.4010908@gmail.com \
    --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).