Messages in this thread | | | Date | Tue, 6 Oct 2009 12:22:43 -0700 | From | Joel Becker <> | Subject | Re: Linux 2.6.32-rc3 |
| |
On Tue, Oct 06, 2009 at 09:31:03AM -0700, Linus Torvalds wrote: > On Tue, 6 Oct 2009, Linus Torvalds wrote: > > > > Unless: > > > > > _That_ i think is a lot harder to confuse with the real .31 than a > > > v2.6.31-1234-g16123c4 version string. > > > > .. are you saying that it would be just some automatically generated > > thing, just a crippled form of CONFIG_LOCALVERSION_AUTO? Kind of a > > CONFIG_LOCALVERSION_AUTO_SHORTFORM? > > So how about this? > > It changes how CONFIG_LOCALVERSION_AUTO works, in the following trivial > way: > > - if it is set, things work the way they always have, and you get a > extended kernel release like > > 2.6.32-rc3-00052-g0eca52a-dirty > > - but if it is _not_ set, we'll still try to get a version from the > underlying SCM (we actually support git, hg and SVN right now, even if > some comments may say "git only"), and if the underlying SCM says it > has a local version, we append just "+", so you get a version number > like > > 2.6.32-rc3+
I really like this, because I don't want to see LOCALVERSION_AUTO forced on. While I like LOCALVERSION_AUTO in theory, in practice it means that a one-line commit forces me to install an entirely new /lib/modules directory. On many of my test machines this fills up quickly. So I turn of LOCALVERSION_AUTO and just set a manual LOCALVERSION.
Joel
--
Life's Little Instruction Book #356
"Be there when people need you."
Joel Becker Principal Software Developer Oracle E-mail: joel.becker@oracle.com Phone: (650) 506-8127
| |