linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Johannes Weiner <jweiner@redhat.com>, quilt-dev@nongnu.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Michal Hocko <mhocko@suse.cz>,
	akpm@linux-foundation.org, mm-commits@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-fsdevel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: mmotm 2011-08-24-14-08 uploaded
Date: Thu, 25 Aug 2011 10:12:55 -0700	[thread overview]
Message-ID: <20110825101255.15436784.rdunlap@xenotime.net> (raw)
In-Reply-To: <20110825154538.GA5860@redhat.com>

On Thu, 25 Aug 2011 17:45:38 +0200 Johannes Weiner wrote:

> On Fri, Aug 26, 2011 at 01:09:38AM +1000, Stephen Rothwell wrote:
> > Hi,
> > 
> > On Thu, 25 Aug 2011 16:07:01 +0200 Michal Hocko <mhocko@suse.cz> wrote:
> > >
> > > On Thu 25-08-11 15:51:03, Michal Hocko wrote:
> > > > 
> > > > On Wed 24-08-11 14:09:05, Andrew Morton wrote:
> > > > > The mm-of-the-moment snapshot 2011-08-24-14-08 has been uploaded to
> > > > > 
> > > > >    http://userweb.kernel.org/~akpm/mmotm/
> > > > 
> > > > I have just downloaded your tree and cannot quilt it up. I am getting:
> > > > [...]
> > > > patching file tools/power/cpupower/debug/x86_64/centrino-decode.c
> > > > Hunk #1 FAILED at 1.
> > > > File tools/power/cpupower/debug/x86_64/centrino-decode.c is not empty after patch, as expected
> > > > 1 out of 1 hunk FAILED -- rejects in file tools/power/cpupower/debug/x86_64/centrino-decode.c
> > > > patching file tools/power/cpupower/debug/x86_64/powernow-k8-decode.c
> > > > Hunk #1 FAILED at 1.
> > > > File tools/power/cpupower/debug/x86_64/powernow-k8-decode.c is not empty after patch, as expected
> > > > 1 out of 1 hunk FAILED -- rejects in file tools/power/cpupower/debug/x86_64/powernow-k8-decode.c
> > > > [...]
> > > > patching file virt/kvm/iommu.c
> > > > Patch linux-next.patch does not apply (enforce with -f)
> > > > 
> > > > Is this a patch (I am using 2.6.1) issue? The failing hunk looks as
> > > > follows:
> > > > --- a/tools/power/cpupower/debug/x86_64/centrino-decode.c
> > > > +++ /dev/null
> > > > @@ -1 +0,0 @@
> > > > -../i386/centrino-decode.c
> > > > \ No newline at end of file
> > > 
> > > Isn't this just a special form of git (clever) diff to spare some lines
> > > when the file deleted? Or is the patch simply corrupted?
> > > Anyway, my patch doesn't cope with that. Any hint what to do about it?
> > 
> > Those files were symlinks and were removed by a commit in linux-next.
> > diff/patch does not cope with that.
> 
> You can probably replace `patch' in your $PATH by a wrapper that uses
> git-apply, which can deal with them.
> 
> Or you could use git-quiltimport, which uses git-apply, to prepare the
> -mmotm base tree in git, on top of which you can continue to work with
> quilt.
> 
> I do this with a cron-job automatically, you can find the result here:
> 
>     http://git.kernel.org/?p=linux/kernel/git/hannes/linux-mmotm.git;a=summary
> 
> If you want to do it manually, there is sometimes confusing binary
> file patch sections in -mmotm, which in turn git-apply can not deal
> with, so I use the following uncrapdiff.awk filter on the patches
> before import.


I thought that I recently saw a reference to an unreleased version of quilt
that handles git symlinks.  Was I dreaming?
or where is it?

Thanks.

> ---
> 
> # Filter out sections that feature an index line but
> # no real diff part that would start with '--- file'
> 
> {
> 	if (HEADER ~ /^diff --git /) {
> 		if ($0 ~ /^index /) {
> 			INDEX=$0
> 		} else if ($0 ~ /^diff --git /) {
> 			print(HEADER)
> 			HEADER=$0
> 		} else if (INDEX ~ /^index /) {
> 			if ($0 ~ /^--- /) {
> 				print(HEADER)
> 				print(INDEX)
> 				print($0)
> 			}
> 			HEADER=""
> 			INDEX=""
> 		} else {
> 			HEADER=HEADER "\n" $0
> 		}
> 	} else if ($0 ~ /^diff --git /) {
> 		HEADER=$0
> 	} else {
> 		print($0)
> 	}
> }
> 
> ---

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-08-25 17:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 21:09 mmotm 2011-08-24-14-08 uploaded akpm
2011-08-24 22:04 ` Randy Dunlap
2011-08-24 22:08   ` Randy Dunlap
2011-08-24 22:11   ` Andrew Morton
2011-08-25  7:13 ` KAMEZAWA Hiroyuki
2011-08-25 15:18   ` Randy Dunlap
2011-08-25 13:51 ` Michal Hocko
2011-08-25 14:07   ` Michal Hocko
2011-08-25 15:09     ` Stephen Rothwell
2011-08-25 15:45       ` Johannes Weiner
2011-08-25 17:12         ` Randy Dunlap [this message]
2011-08-26  7:21         ` Michal Hocko
2011-08-25 19:23   ` Andrew Morton

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=20110825101255.15436784.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=akpm@linux-foundation.org \
    --cc=jweiner@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=mm-commits@vger.kernel.org \
    --cc=quilt-dev@nongnu.org \
    --cc=sfr@canb.auug.org.au \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).