From: Oleg Drokin <green@namesys.com>
To: Chris Mason <mason@suse.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Symbol collisions in patch?
Date: Wed, 3 Apr 2002 17:43:01 +0400 [thread overview]
Message-ID: <20020403174301.A1421@namesys.com> (raw)
In-Reply-To: <1017841106.26533.92.camel@tiny>
Hello!
On Wed, Apr 03, 2002 at 08:38:26AM -0500, Chris Mason wrote:
> > One of teh best ways to convice Hans to provice v3.6 support in 2.2 kernels
> > is to pay for the work (details are at http://www.namesys.com/support.html)
> Tom, putting the 3.6.x format into the 2.2.x code is a huge amount of
> work. It took us months to get things stable in 2.4.x. If anyone on
> the list wants to do the port, I'll supply beer for the party when
> you're done.
Offer the 2-way ticket to US, and I might think about your offer ;)
Bye,
Oleg
next prev parent reply other threads:[~2002-04-03 13:43 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 [this message]
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
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=20020403174301.A1421@namesys.com \
--to=green@namesys.com \
--cc=mason@suse.com \
--cc=reiserfs-list@namesys.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 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.