LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Kevin Winchester <kjwinchester@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mm snapshot broken-out-2007-11-13-04-14.tar.gz uploaded
Date: Tue, 13 Nov 2007 17:11:13 -0800	[thread overview]
Message-ID: <20071113171113.06f2b26f.akpm@linux-foundation.org> (raw)
In-Reply-To: <200711132020.33124.kjwinchester@gmail.com>

On Tue, 13 Nov 2007 20:20:32 -0400 Kevin Winchester <kjwinchester@gmail.com> wrote:

> On November 13, 2007 08:15:41 am akpm@linux-foundation.org wrote:
> > The mm snapshot broken-out-2007-11-13-04-14.tar.gz has been uploaded to
> >
> >   
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/broken-out-2007-11-13-
> >04-14.tar.gz
> >
> > It contains the following patches against 2.6.24-rc2:
> >
> 
> <snip>
> 
> How exactly do I go about trying out this snapshot?  I did the following:
> 
> - exported 2.6.24-rc2 from my cloned git tree to a separate folder
> - installed quilt
> - extracted the patches to the "patches" directory at the top level of the 
> 2.6.24-rc2 tree
> - copied the list of patches from your mail into a "series" file which I 
> placed in the "patches" directory

The tarball contains a copy of the series file.  For some reason LARGE
numbers of people miss it and ask me "hey, where's the series file?".  Odd.

> - ran "quilt push -a"
> 
> The result was that all of the patches seem to have been applied, but there 
> were many offsets and at least one fuzzed patch.  Should they have applied 
> cleanly?  Is quilt the way I am supposed to be applying these patches?

Yes, the -mm patches contain large amount of fuzz.  I'll occasionally go in
and do a mass defuzzing (shaving?) but it all goes fuzzy again within a
day.

I _could_ rediff all the time, but I keep all the patches under revision
control and I often need to grab the previous version of a patch (when I've
just dropped an earlier patch, and that earlier patch had caused me to redo
this patch).  Having lots of revisions due to unnecessary rediffing would
complicate that.

>  Is 
> there a reason that there is no "series" file in the archive with the 
> patches?

It's in there ;)

btw, I put the patches in a directory called "broken-out" so that you can
untar them in your kernel tree and not have them stomped all over your
existing patches/ directory.  symlink it...


  reply	other threads:[~2007-11-14  1:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 12:15 akpm
2007-11-13 12:40 ` cscope build warning [Was: mm snapshot broken-out-2007-11-13-04-14.tar.gz uploaded] Jiri Slaby
2007-11-13 13:27   ` Sam Ravnborg
2007-11-13 13:36     ` Jiri Slaby
2007-11-13 12:50 ` nfs functions undefined " Jiri Slaby
2007-11-13 17:34   ` [PATCH] " Randy Dunlap
2007-11-13 19:43     ` Andrew Morton
2007-11-13 14:43 ` mm snapshot broken-out-2007-11-13-04-14 Build Fails at memory.c Kamalesh Babulal
2007-11-13 15:17   ` Martin Schwidefsky
2007-11-13 15:30     ` Kamalesh Babulal
2007-11-13 15:29   ` Martin Schwidefsky
2007-11-13 15:11 ` mm snapshot broken-out-2007-11-13-04-14 Build Fails due kobject cleanup Kamalesh Babulal
2007-11-13 15:22 ` mm snapshot broken-out-2007-11-13-04-14 Build Fails due kobject cleanup (Resend) Kamalesh Babulal
2007-11-13 19:51 ` mm snapshot broken-out-2007-11-13-04-14 Build Fails - linking when !CONFIG_NFS_V4 Kamalesh Babulal
2007-11-14  5:23   ` Randy Dunlap
2007-11-14  0:20 ` mm snapshot broken-out-2007-11-13-04-14.tar.gz uploaded Kevin Winchester
2007-11-14  1:11   ` Andrew Morton [this message]
2007-11-14  1:15     ` Randy Dunlap
2007-11-13 15:21 Al Boldi
2007-11-13 15:26 ` Peter Zijlstra
2007-11-13 16:42   ` Al Boldi
2007-11-13 21:43     ` Valdis.Kletnieks
2007-11-14  5:09       ` Al Boldi

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=20071113171113.06f2b26f.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=kjwinchester@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: mm snapshot broken-out-2007-11-13-04-14.tar.gz uploaded' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).