[PATCH v3 0/7] prepare new nanddump options, defaults

Brian Norris computersforpeace at gmail.com
Thu Jun 23 19:00:37 EDT 2011

On Thu, Jun 23, 2011 at 8:52 AM, Mike Frysinger <vapier.adi at gmail.com> wrote:
> On Thu, Jun 23, 2011 at 11:04, Artem Bityutskiy wrote:
>> And speaking about released, should we do a new one?

Yes, I think so. Then I can eliminate all those warnings and finish my changes!

>> If you see that
>> some utils should have a version increased - feel free to do so.

I think the nanddump, mtdinfo, and flash_{lock, unlock} tools have had
plenty of updates to warrant a bump...but flash_{lock, unlock} doesn't
have a version number (neither do many of the utils). I'll send a
patch for bumping soon...then should the release tag come afterward?

>> But
>> even better we could make the version numbers to be the same as release
>> number, then this process would be more automated and version would make
>> some sense...
> the version isnt encoded anywhere.  so if you started using something
> like the kernel where the VERSION was in the Makefile, we could use
> that to create a header file which all the utils would include.
> -mike

I like Mike's idea on the VERSION thing. Unfortunately, few utils
display any version number at all, and of the ones that do, we have a
random "2.1.0" from flash_erase. We wouldn't want to have a decreased
version number...so do we jump to mtd-utils v2.1 and make everything
the same version? Or even v3.0, just for fun?

If we're going for 2.1 (or some other similarly large jump), maybe we
should do the following:
1) increment some individual version numbers (nanddump and mtdinfo only?)
2) make a mtd-utils release 1.4.6
3) take care of all the "feature-removal-schedule" stuff...
4) put the VERSION in the Makefile (still version 1.4.6), have it
generate a header
5) include that header in common.h
6) add a stub version function in common.h that would utilize this
basic info to supply a "--version" option to all utilities that don't
have one (at least, as far as reasonable...)
7) release another mtd-utils, jumping to v2.x (only needing to edit
Makefile for version increments!)

How does this sound?


More information about the linux-mtd mailing list