On Friday 09 March 2007 08:29, Vitaly Wool wrote:
> Hello Charles,
>
> On 3/8/07, Johnson, Charles F <charles.f.johnson@intel.com> wrote:
> > This is great news. Any estimates on when you might be ready to push
> > this into the main linux upstream? Is this now considered the official
> > YAFFS2 repository?
>
> I'd think that the official yaffs repo will remain the CVS one. I'll
> be working on a kind of 'unstable' version to adapt things to mainline
> requirements.
We will need to discuss thi further, but I think that the "official"
repository will be in cvs.
I am very much a git newbie, but my understanding is that the git will be kept
ready for the current kernel, which includes removal of legacy #if code.
YAFFS is priomarily used in embedded space where people tend to use older
kernels and only move kernels with very good reason. There are a lot of
embedded folk still using 2.4.x. I do not think it useful to drop support for
those kernels or for yaffs direct.
My understanding of the way this will work is this:
*The CVS codebase will be the the official repository and continue to be for
all players, including legacy and non-Linux (as it is now).
* git will be kept the same as CVS (perhaps with some minor lags for stability
etc), except pared down to remove anything that is not relevant to the
current kernel.
In short, git is there to provide a way to integrate YAFFS into mainstream
kernel, otherwise it is business as usual.
>
> As of the estimation, I'm not sure now -- let's see how it goes for
> about two weeks and then I guess we'll have a bettet idea about how it
> goes.
I agree. Some of this will be learning on the job.
-- Charles
(text/plain)