Git development
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Andrew Morton <akpm@osdl.org>, Git Mailing List <git@vger.kernel.org>
Subject: Re: [GIT PULL] ARM updates
Date: Wed, 8 Jun 2005 08:15:09 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0506080802150.2286@ppc970.osdl.org> (raw)
In-Reply-To: <20050608143549.GA7074@dyn-67.arm.linux.org.uk>



On Wed, 8 Jun 2005, Russell King wrote:
> 
> Please incorporate the latest ARM changes, which can be found at:
> 
> 	master.kernel.org:/home/rmk/linux-2.6-arm.git

Heh, this one showed a problem with some git-apply sanity checks (I use 
"git-apply --stat" to generate the diffstat). 

In particular:

> This will update the following files:
> 
>  arch/arm/mm/minicache.c                |   73 ------------------

You didn't actually delete the file, you made it be zero-sized. Which made 
the patch header be

  diff --git a/arch/arm/mm/minicache.c b/arch/arm/mm/minicache.c
  --- a/arch/arm/mm/minicache.c
  +++ b/arch/arm/mm/minicache.c
  @@ -1,73 +0,0 @@
  ...

and git-apply complains about the fact that the patch deletes the file,
but the file still exists (it can tell both from this: it sees that this
is not a "delete" event, since a "diff --git" would have had a "delete"
header line in it, but it also sees that it's a delete because the patch
has no result lines, ie the final "+0,0" means that there was nothing
left).

Now, git-apply shouldn't actually care _that_ deeply in general, but the 
reason I added that check was exactly because in Linux, I actually want 
zero-sized files to not exist, and it turns out that git-apply did catch 
it..

Anyway, I've made git-apply warn in a nice way (instead of claiming the 
patch is corrupt and exiting), but it did point out that you left 
minixache.c empty, not deleted.

In contrast, the "copypage-xscale.S" file really _was_ deleted by your 
changes, not just made empty.

Russell, do you know why you sometimes generate empty files, and sometimes 
delete them? If you use "patch", add the "-E" flag to it..

		Linus

       reply	other threads:[~2005-06-08 15:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050608143549.GA7074@dyn-67.arm.linux.org.uk>
2005-06-08 15:15 ` Linus Torvalds [this message]
2005-06-08 16:06   ` [GIT PULL] ARM updates Russell King

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=Pine.LNX.4.58.0506080802150.2286@ppc970.osdl.org \
    --to=torvalds@osdl.org \
    --cc=akpm@osdl.org \
    --cc=git@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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