From: Oleg Drokin <green@namesys.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org, reiserfs-dev@namesys.com
Subject: Re: [reiserfs-dev] [PATCH] Suppress compilation warnings on big endian platform for reiserfs
Date: Wed, 9 Jan 2002 20:03:40 +0300 [thread overview]
Message-ID: <20020109200340.A2123@namesys.com> (raw)
In-Reply-To: <20020109173056.B1161@namesys.com> <Pine.LNX.4.21.0201091343560.20977-100000@freak.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0201091343560.20977-100000@freak.distro.conectiva>
Hello!
Sure, I can. Reason for sending small patches, is because Linus have requested people to send stuff in that way.
BTW, do you mean you won't accept any more patches until 2.4.19-pre1? (or what -pre1 do you mean?)
Bye,
Oleg
On Wed, Jan 09, 2002 at 01:44:53PM -0200, Marcelo Tosatti wrote:
>
> Oleg,
>
> Can you please queue all of this patches for the next -pre1 in one big
> update instead sending me a lot of daily small
>
> On Wed, 9 Jan 2002, Oleg Drokin wrote:
>
> > Hello!
> >
> > Argh! Stupid typo have flipped into the previous incarnation of this patch, so here is correct one.
> > Please apply this one.
> >
> > Bye,
> > Oleg
> > On Wed, Jan 09, 2002 at 05:03:03PM +0300, Oleg Drokin wrote:
> > > Please apply.
> >
>
next prev parent reply other threads:[~2002-01-09 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 14:03 [PATCH] Suppress compilation warnings on big endian platform for reiserfs Oleg Drokin
2002-01-09 14:30 ` [reiserfs-dev] " Oleg Drokin
2002-01-09 15:44 ` Marcelo Tosatti
2002-01-09 15:47 ` Marcelo Tosatti
2002-01-09 17:03 ` Oleg Drokin [this message]
2002-01-09 15:56 ` Marcelo Tosatti
2002-01-09 17:12 ` Oleg Drokin
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=20020109200340.A2123@namesys.com \
--to=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=reiserfs-dev@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.