All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Knigge <Michael.Knigge@set-software.de>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Frank Cusack <fcusack@fcusack.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.21-rc8
Date: Thu, 12 Jun 2003 06:27:46 GMT	[thread overview]
Message-ID: <20030612.6274686@knigge.local.net> (raw)
In-Reply-To: <Pine.LNX.4.55L.0306111815100.31893@freak.distro.conectiva>

Hi,

> > > Ugh, no fix for nfs_unlink/sillyrename?
> >
> > Damn, right. I'll take a look at it and release -rc9 today or wait for
> > 2.4.22pre.

> It seems this will have to wait for 2.4.22pre.


Hmmm... I don't want to tell you how you have to do your job, but this 
is a known error and (if I followed the postings here correctly) there 
was a fix posted. So why not include it in 2.4.22?

imho the patch have to be included in 2.4.21 and (imho) it is a bad 
practice to release a piece of software with a known bug (especially 
if a fix is available).


Bye
  Michael







  reply	other threads:[~2003-06-12  6:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-10 22:06 Linux 2.4.21-rc8 Marcelo Tosatti
2003-06-10 23:56 ` Frank Cusack
2003-06-11  0:10   ` Marcelo Tosatti
2003-06-11 21:15     ` Marcelo Tosatti
2003-06-12  6:27       ` Michael Knigge [this message]
2003-06-12  7:56         ` Jörn Engel
2003-06-12  8:09         ` Arjan van de Ven
2003-06-12 18:46           ` Aschwin Marsman
2003-06-12  8:17         ` jw schultz
2003-06-11  4:39 ` Lucas Correia Villa Real
2003-06-12 22:23 ` Jerome Chantelauze
2003-06-13  9:31   ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2003-06-12  8:59 John Bradford
2003-06-12 16:30 ` iain d broadfoot
2003-06-13 11:29 ` Stephan von Krawczynski

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=20030612.6274686@knigge.local.net \
    --to=michael.knigge@set-software.de \
    --cc=fcusack@fcusack.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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.