All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Wysochanski <davidw@netapp.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Getting close to RHEL4 U3 freeze
Date: Thu, 03 Nov 2005 18:27:23 -0500	[thread overview]
Message-ID: <436A9CDB.1060606@netapp.com> (raw)
In-Reply-To: <20051024170054.GC19176@phlogiston.msp.redhat.com>

When's the freeze?

I have a path priority patch (for netapp targets) I'm trying to get
tested so I can submit it.  It's purely new code in userspace (patch
against multipath-tools), so hopefully non-controversial.

Not sure if I should kill myself or not, hence the question about
whether I've missed U3 freeze yet.

Thanks.

Benjamin Marzinski wrote:
> Just to let everybody know that freeze date for Redhat Enterprise Linux 4
> Update 3 is getting close.  The blocker bug that is currently being used to
> track bugfixes and enhancements that are getting into U3 is
> 
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=171044
> 
> If anyone feels strongly that there is a bugzilla that should be on the list,
> but is not, please put a comment in the 171044 bugzilla entry.  If it's an
> enhancement, please make sure that the enhancement description is as specific
> as possible.
> 
> Thanks
> 
> -Ben
> 
> -- 
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
> 

  parent reply	other threads:[~2005-11-03 23:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-24 17:00 Getting close to RHEL4 U3 freeze Benjamin Marzinski
2005-10-24 17:07 ` Brian Long
2005-11-03 23:27 ` David Wysochanski [this message]
2005-11-07 19:17   ` Benjamin Marzinski

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=436A9CDB.1060606@netapp.com \
    --to=davidw@netapp.com \
    --cc=dm-devel@redhat.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.