lkml.org 
[lkml]   [2009]   [Oct]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: Linux 2.6.32-rc3
    From
    Date
    On Mon, 2009-10-05 at 21:57 -0400, Len Brown wrote:
    > > do you mean -rc2 as in the Makefile (ie really -rc1) or -rc2 as in the
    > > tagged release.
    >
    > We have a similar problem with the period between, say, 2.6.X and
    > 2.6.Y-rc1. The Makefile still says 2.6.X, yet during the 2.6.Y
    > merge window the tree is very different from 2.6.X.
    >
    > This confuses things like my scripts that take a source tree tarball,
    > and (re)generate config files for build testing based on the tags
    > in the Makefile. There is no way for the scripts to know the
    > post 2.6.X tree not the same as 2.6.X itself, the new configs
    > overwrite the old, overwrite the old results etc.
    >
    > I think that BenH also had troubles with this issue and pointed
    > it out a while back, but you were not convinced at the time that
    > it was a problem worth solving.
    >
    > This could be clarified if you update Makefile on the 1st commit
    > after 2.6.X is frozen to simply be 2.6.Y-merge or 2.6.Y-rc0
    > or something. Anything but 2.6.X.

    I have seen this request many times and it seems to make perfect sense.
    The first commit applied after a release should change the version
    number to "something" - and "2.6.next-rc0" sounds as good as anything
    else that has been proposed so far.

    /D

    --
    Dirk Hohndel
    Intel Open Source Technology Center



    \
     
     \ /
      Last update: 2009-10-06 04:57    [W:0.022 / U:0.284 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site