Re: Arrr! Linux v2.6.14-rc2

From: Sean (seanlkml_at_sympatico.ca)
Date: 09/21/05

  • Next message: Hideo AOKI: "[PATCH 2.6.14-rc1-mm1] mm: OVERCOMMIT_GUESS considers lowmem_reserve_ratio." 
    Date:	Wed, 21 Sep 2005 15:06:42 -0400 (EDT)
To: "Bill Davidsen" <davidsen@tmr.com>

    On Wed, September 21, 2005 2:28 pm, Bill Davidsen said:

    > But that pulls the current tree, doesn't it? Not the git release?

    It pulls the latest git release plus any extra commits that have been made
    since, if any. Now, if you have a specific reason to test a -gitX
    release you can simply lookup which commit corresponds to the -gitX
    release and check it out of the git repository and build it. Actually, I
    just posted a script that lets you check out a build by -gitX name instead
    of having to manually lookup the corresponding commit id.

    > For purposes of bug reporting and fixing, I would think that having some
    > reproducible version is superior. If I say git3, anyone can get it, it
    > would appear that "git pull" isn't as deterministic.

    There are cases where using the -gitX release helps a bit. But there's
    nothing magic about a -gitX release, it's just a collection of whatever
    commits existed when the timed build procedure ran.

    Using git you get the choice of using -gitX builds or tracking directly
    from the most recent commit as the situation demands. Therefore if Linus
    commits a fix beyond the latest -gitX release you happen to need, you're
    good to go. If you want to track the latest -gitX release, you can do
    that with git too.

    Sean

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Hideo AOKI: "[PATCH 2.6.14-rc1-mm1] mm: OVERCOMMIT_GUESS considers lowmem_reserve_ratio."

    Relevant Pages

    • Re: Git training wheels for the pimple faced maintainer
      ... Git keeps track of the fork-point, ... merge-point, and as such a "diff" from ... because merging from me obviously brings in commits ... git log -p linux..for-linus | diffstat ...
      (Linux-Kernel)
    • Re: Linux 2.6.32-rc3
      ... compiled a dirty kernel that has something that isn't committed). ... entirely from the tags in the git tree, and do it entirely that way. ... commits after 2.6.32-rc2. ... Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • Re: 2.6.12 hangs on boot
      ... Since you seem to be a git user, maybe you could try the git ... > rather than all the commits in between those kernel versions. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH] x86: kill arch/x86/kernel/mpparse.c debugging printk.
      ... sure - but some other commits were queued already so i've applied the ... delta fix below. ... $ git format-patch -o tmp HEAD~n ...
      (Linux-Kernel)
    • patch style checks
      ... scripts/spot-common-mistakes. ... about newly-added code which has busted ... As an experiment I took the -mm git repo and applied a modified versions ... individual commits there also. ...
      (Linux-Kernel)