All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Krause <manuel.krause@mb.tu-ilmenau.de>
To: Chris Mason <mason@suse.com>
Cc: reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: 2.4.19-pending is pending
Date: Tue, 06 Aug 2002 02:23:16 +0200	[thread overview]
Message-ID: <3D4F16F4.9060802@mb.tu-ilmenau.de> (raw)
In-Reply-To: 1028592182.1759.300.camel@tiny

On 08/06/2002 02:03 AM, Chris Mason wrote:
> On Mon, 2002-08-05 at 19:28, Manuel Krause wrote:
> 
>>Hey ReiserFS-team,
>>
>>come on, fill
>>    ftp://ftp.namesys.com/pub/reiserfs-for-2.4/2.4.19.pending
>>with life/patches, please!
>>
>>I can't calm down and get back to my rock-solid patience until the hold 
>>back patches come out... ;-)
> 
> 
> Step one was getting the commit_super patch into the kernel, I sent that
> this morning.  All of the data logging stuff depends on it, and we
> wanted to get the major changes in first.
> 
> -chris
> 

Seems you have priority on Marcelos task list? ;-) Very nice! Push them 
all!!!

But, err,  I wanted the old
   ftp://ftp.namesys.com/pub/reiserfs-for-2.4/2.4.19-pre7.pending
things to be actualized and also Olegs previously mentioned "hidden" 
ones to appear at least on the namesys server...

Olegs messages made me think of hundreds kB of namesys patches to come 
additionally to yours and the old ones...

Dunno, why we shouldn't have tried "them" until now, on rational base...


Best wishes,

Manuel



  reply	other threads:[~2002-08-06  0:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-05 23:28 2.4.19-pending is pending Manuel Krause
2002-08-06  0:03 ` Chris Mason
2002-08-06  0:23   ` Manuel Krause [this message]
2002-08-06  0:37     ` Manuel Krause
2002-08-06  1:06       ` Chris Mason
2002-08-06  0:40     ` Chris Mason
2002-08-06  5:13       ` Oleg Drokin
2002-08-06 13:49         ` Newsmail

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=3D4F16F4.9060802@mb.tu-ilmenau.de \
    --to=manuel.krause@mb.tu-ilmenau.de \
    --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.