From: Daniel Jacobowitz <dan@debian.org>
To: Maciej Soltysiak <solt2@dns.toxicfilms.tv>
Cc: linux-kernel@vger.kernel.org
Subject: Re: strange incremental patch size [2.6.12-rc2 to 2.6.12-rc3]
Date: Thu, 21 Apr 2005 09:48:31 -0400 [thread overview]
Message-ID: <20050421134831.GA30943@nevyn.them.org> (raw)
In-Reply-To: <1617591394.20050421123259@dns.toxicfilms.tv>
On Thu, Apr 21, 2005 at 12:32:59PM +0200, Maciej Soltysiak wrote:
> Hi,
>
> These are the sizes of rc2 and rc3 patches
>
> # ls -la patch-2.6.12*
> -rw-r--r-- 1 root src 18011382 Apr 4 18:50 patch-2.6.12-rc2
> -rw-r--r-- 1 root src 19979854 Apr 21 02:29 patch-2.6.12-rc3
>
> Let us make an incremental patch from rc2 to rc3
>
> # interdiff patch-2.6.12-rc2 patch-2.6.12-rc3 >x
>
> Let us see how big it is.
> # ls -ld x
> -rw-r--r-- 1 root src 37421924 Apr 21 12:28 x
>
> How come interdiff from rc2 (18MB) to rc3 (20MB) gave me
> 37MB worth of patch-code ? I would expect something about
> 2MB but 40MB ?
Try interdiff -p1?
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-04-21 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 10:32 strange incremental patch size [2.6.12-rc2 to 2.6.12-rc3] Maciej Soltysiak
2005-04-21 11:05 ` Joost Remijn
2005-04-21 13:48 ` Daniel Jacobowitz [this message]
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=20050421134831.GA30943@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=solt2@dns.toxicfilms.tv \
/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