From: Sunil Mushran <Sunil.Mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [git patches] ocfs2 fixes
Date: Wed, 21 Jun 2006 12:17:31 -0700 [thread overview]
Message-ID: <44999B4B.6000500@oracle.com> (raw)
In-Reply-To: <1150916457.5288.63.camel@brilong-lnx>
Typically all bugs are fixed on 1.2.x and then rolled forward to git.
Features follow the opposite route.
We don't yet have a date for 1.2.2.
Brian Long wrote:
> On Wed, 2006-06-21 at 11:43 -0700, Mark Fasheh wrote:
>
>> Please pull from 'upstream-linus' branch of
>> git://git.kernel.org/pub/scm/linux/kernel/git/mfasheh/ocfs2.git
>>
>> to receive the following updates:
>>
>> fs/ocfs2/dlm/dlmast.c | 12
>> fs/ocfs2/dlm/dlmcommon.h | 63 ++++
>> fs/ocfs2/dlm/dlmconvert.c | 24 +
>> fs/ocfs2/dlm/dlmdebug.c | 6
>> fs/ocfs2/dlm/dlmdebug.h | 30 --
>> fs/ocfs2/dlm/dlmdomain.c | 101 +++++--
>> fs/ocfs2/dlm/dlmfs.c | 6
>> fs/ocfs2/dlm/dlmlock.c | 68 ++++-
>> fs/ocfs2/dlm/dlmmaster.c | 448 +++++++++++++++++++++++-----------
>> fs/ocfs2/dlm/dlmrecovery.c | 580 ++++++++++++++++++++++++++++++++++-----------
>> fs/ocfs2/dlm/dlmthread.c | 68 ++++-
>> fs/ocfs2/dlm/dlmunlock.c | 10
>> fs/ocfs2/dlm/userdlm.c | 2
>> 13 files changed, 1045 insertions(+), 373 deletions(-)
>>
>
> Hi Mark et al,
>
> When you send a huge patch like this to Linus, can we assume all these
> patches are already integrated into the released RPMs on
> http://oss.oracle.com for RHEL 4?
>
> Also, what is your typical release schedule for rolling up bugs and
> releasing a point release? For example, I see in
> http://oss.oracle.com/~smushran/.ocfs2-1.2.1-3/README that this version
> is there until 1.2.2 is released? Do you have a target for 1.2.2? Will
> it include other bug fixes?
>
> /Brian/
>
next prev parent reply other threads:[~2006-06-21 19:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 18:43 [Ocfs2-devel] [git patches] ocfs2 fixes Mark Fasheh
2006-06-21 18:43 ` Mark Fasheh
2006-06-21 19:00 ` [Ocfs2-devel] " Brian Long
2006-06-21 19:17 ` Sunil Mushran [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-13 17:14 [Ocfs2-devel] [git patches] Ocfs2 fixes Mark Fasheh
2008-12-17 19:34 Mark Fasheh
2008-12-01 22:54 Mark Fasheh
2008-11-04 18:32 Mark Fasheh
2008-06-16 20:12 Mark Fasheh
2008-06-01 16:16 Mark Fasheh
2008-05-02 18:35 Mark Fasheh
2008-03-10 15:46 [Ocfs2-devel] [git patches] ocfs2 fixes Mark Fasheh
2008-03-04 10:47 Mark Fasheh
2007-12-17 11:00 Mark Fasheh
2007-11-27 17:16 Mark Fasheh
2007-11-07 9:41 Mark Fasheh
2007-09-21 9:36 Mark Fasheh
2007-09-11 15:32 Mark Fasheh
2007-06-08 10:48 Mark Fasheh
2007-05-03 11:57 Mark Fasheh
2007-03-28 13:29 Mark Fasheh
2007-02-02 9:28 Mark Fasheh
2007-01-29 12:05 Mark Fasheh
2007-01-29 13:19 ` Mark Fasheh
2007-01-29 21:19 ` Mark Fasheh
2007-01-22 11:02 Mark Fasheh
2006-12-29 15:18 Mark Fasheh
2006-06-19 18:46 Mark Fasheh
2006-05-17 22:21 Mark Fasheh
2006-05-12 0:21 Mark Fasheh
2006-04-10 23:03 Mark Fasheh
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=44999B4B.6000500@oracle.com \
--to=sunil.mushran@oracle.com \
--cc=ocfs2-devel@oss.oracle.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.