All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: doiggl@velocitynet.com.au
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: next major release query
Date: Wed, 20 Aug 2008 23:54:50 +0400	[thread overview]
Message-ID: <48AC768A.8040909@gmail.com> (raw)
In-Reply-To: <17724.202.168.22.19.1219239253.squirrel@webmail.velocity.net.au>

doiggl@velocitynet.com.au wrote:
> Hello,
>   

Hello.

> I notice on
> http://www.kernel.org/pub/linux/kernel/people/edward/reiser4/reiser4-for-2.6/
>   

This directory is for patches against vanilla kernels.

Actually, these patches are synchronizations with -mm tree.
If many essential changes in -mm are accumulated, then we
release a "revision" as reiser4-for-2.6.2x.y.patch

We don't prepare patches against -rc kernels:
If you need this, then feel free to do it by yourself, actively using
-mm sources. Since reiser4 is in -mm tree, preparing such patches
is a task of complexity O(1) ;)

> it is at the reiser4-for-2.6.25.* revision/level.
>
> Questions:
> - What do you think the next major revision will be ?
>   

I think it will be something like reiser4-for-2.6.27

Thanks,ward.

> - Will it include all patches up to a point in time, of your choosing ?
>
> Thanks for the info.
> Glenn
>
> --
> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>   


  parent reply	other threads:[~2008-08-20 19:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20 13:34 next major release query doiggl
2008-08-20 16:19 ` Ryan Hope
2008-08-20 19:32   ` Christian Stroetmann
2008-08-20 19:54 ` Edward Shishkin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-08-20 20:30 devsk
2008-08-20 21:11 ` Edward Shishkin

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=48AC768A.8040909@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=doiggl@velocitynet.com.au \
    --cc=reiserfs-devel@vger.kernel.org \
    /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.