public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Bernhard Priewasser <bernhard.priewasser@in2soft.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2: Releases? Versions?
Date: Thu, 21 Jul 2005 10:13:10 -0400	[thread overview]
Message-ID: <1121955191.20077.22.camel@localhost.localdomain> (raw)
In-Reply-To: <42DF4A22.4060705@in2soft.de>

On Thu, 2005-07-21 at 09:09 +0200, Bernhard Priewasser wrote:
> i have just a simple question about JFFS2 & versioning. Too simple 
> perhaps... please be patient with me...
> 
> I'm confused about the version numbers of JFFS2, "JFFS2 version 2.2. 
> (NAND)" (out of a dmesg / boot) for example.

Those version numbers are very infrequently updated. We started at 2.0,
then updated to 2.1 in the very early days when we had to change the
format. Then the version number remained unchanged for a long time until
the NAND support was added and it was increased to 2.2.

The 2.4 kernel has JFFS2 2.1, and the 2.6 kernel has JFFS2 2.2. These
are the jffs2-2_4-branch and the HEAD of the CVS tree, respectively.

> If source code + CVS available: How can i determine the release version?
> If source code available: How can i determine the release version?
> How can i determine the release of JFFS2 currently running in a kernel?
> Is there some changelog "overview" (not only for single files)?

There isn't really an overall 'version' other than the one described
above, which isn't particularly useful. You can look at the $Id$ tags in
the files though, which will indicate the date on which the snapshot was
taken, if they're using a snapshot from CVS instead of whatever was
present in the kernel they started with.

-- 
dwmw2

  reply	other threads:[~2005-07-21 14:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-21  7:09 JFFS2: Releases? Versions? Bernhard Priewasser
2005-07-21 14:13 ` David Woodhouse [this message]
2005-07-22  7:35   ` Bernhard Priewasser

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=1121955191.20077.22.camel@localhost.localdomain \
    --to=dwmw2@infradead.org \
    --cc=bernhard.priewasser@in2soft.de \
    --cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox