From: Oleg Drokin <green@namesys.com>
To: Tom Oehser <tom@toms.net>
Cc: Adam Goryachev <mailinglists@websitemanagers.com.au>,
reiserfs-list@namesys.com
Subject: Re: Symbol collisions in patch?
Date: Wed, 3 Apr 2002 16:55:32 +0400 [thread overview]
Message-ID: <20020403165532.A1126@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0204030639310.647-100000@conn6m.toms.net>
Hello!
On Wed, Apr 03, 2002 at 06:51:23AM -0500, Tom Oehser wrote:
> > Why spend the next 6 months/12 months (I have no idea how long) developing
> > support for 2.0 and 2.2 kernels with reiserfs when by that stage, even the
> It wouldn't take that long to fix the symbol collisions and apply the
> known-missing patch. It probably wouldn't take that long to backport the
> 3.6 stuff.
Symbol collisions are not going to be fixed at reiserfs side.
Symbol collisions were introduced by ext3 folks.
Bye,
Oleg
next prev parent reply other threads:[~2002-04-03 12:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 2:41 Symbol collisions in patch? Tom Oehser
2002-04-03 5:32 ` Oleg Drokin
2002-04-03 13:38 ` Chris Mason
2002-04-03 13:43 ` Oleg Drokin
2002-04-03 14:02 ` Chris Mason
2002-04-03 14:05 ` Oleg Drokin
2002-04-03 5:54 ` Adrian Phillips
2002-04-03 7:33 ` Adam Goryachev
2002-04-03 11:51 ` Tom Oehser
2002-04-03 12:55 ` Oleg Drokin [this message]
2002-04-03 16:35 ` Chris Mason
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=20020403165532.A1126@namesys.com \
--to=green@namesys.com \
--cc=mailinglists@websitemanagers.com.au \
--cc=reiserfs-list@namesys.com \
--cc=tom@toms.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.