public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.6.18-rc3
Date: Sun, 30 Jul 2006 09:30:34 +0100	[thread overview]
Message-ID: <20060730083034.GA11360@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0607292320490.4168@g5.osdl.org>

There's something weird in this release - object
0021aad5db43ccc0d0356f2f5e4e28446c8b983a appears to change size (or it
does for me.)

Searching 'linux-2.6/.git/' and 'linux-2.6-mmc/.git/' for common objects and hardlinking them...
ERROR: File sizes are not the same, cannot relink linux-2.6/.git/objects/00/21aad5db43ccc0d0356f2f5e4e28446c8b983a to linux-2.6-mmc/.git/objects/00/21aad5db43ccc0d0356f2f5e4e28446c8b983a.
rmk@dyn-67:[git]:<1022> vdir linux-*/.git/objects/00/21aad5db43ccc0d0356f2f5e4e28446c8b983a
-r--r--r-- 1 rmk rmk 6891 Jul 25 19:57 linux-2.6/.git/objects/00/21aad5db43ccc0d0356f2f5e4e28446c8b983a
-r--r--r-- 1 rmk rmk 6862 Jul 25 20:29 linux-2.6-mmc/.git/objects/00/21aad5db43ccc0d0356f2f5e4e28446c8b983a
-r--r--r-- 1 rmk rmk 6862 Jul 25 20:30 linux-2.6-rmk/.git/objects/00/21aad5db43ccc0d0356f2f5e4e28446c8b983a
-r--r--r-- 1 rmk rmk 6862 Jul 25 20:30 linux-2.6-serial/.git/objects/00/21aad5db43ccc0d0356f2f5e4e28446c8b983a
rmk@dyn-67:[git]:<1025> md5sum linux-*/.git/objects/00/21aad5db43ccc0d0356f2f5e4e28446c8b983a
5607142215895de1d71abbff28e3d096  linux-2.6/.git/objects/00/21aad5db43ccc0d0356f2f5e4e28446c8b983a
3af2b33663ce5c53a336bd31d4b469e0  linux-2.6-mmc/.git/objects/00/21aad5db43ccc0d0356f2f5e4e28446c8b983a
3af2b33663ce5c53a336bd31d4b469e0  linux-2.6-rmk/.git/objects/00/21aad5db43ccc0d0356f2f5e4e28446c8b983a
3af2b33663ce5c53a336bd31d4b469e0  linux-2.6-serial/.git/objects/00/21aad5db43ccc0d0356f2f5e4e28446c8b983a

The first tree (linux-2.6) was fetched using rsync from a tree which also
had been obtained via rsync:

src@flint:[linux-2.6]:<1015> vdir .git/objects/00/21aad5db43ccc0d0356f2f5e4e28446c8b983a
-r--r--r--  1 src src 6891 Jul 25 19:57 .git/objects/00/21aad5db43ccc0d0356f2f5e4e28446c8b983a
src@flint:[linux-2.6]:<1016> md5sum .git/objects/00/21aad5db43ccc0d0356f2f5e4e28446c8b983a
5607142215895de1d71abbff28e3d096  .git/objects/00/21aad5db43ccc0d0356f2f5e4e28446c8b983a

And on hera:

[rmk@hera torvalds]$ vdir linux-2.6.git/objects/00/21aad5db43ccc0d0356f2f5e4e28446c8b983a
-r--r--r--  1 torvalds torvalds 6891 Jul 22 00:45 linux-2.6.git/objects/00/21aad5db43ccc0d0356f2f5e4e28446c8b983a
[rmk@hera torvalds]$ md5sum linux-2.6.git/objects/00/21aad5db43ccc0d0356f2f5e4e28446c8b983a
5607142215895de1d71abbff28e3d096  linux-2.6.git/objects/00/21aad5db43ccc0d0356f2f5e4e28446c8b983a

So the act of git fetch-ing from dyn-67's linux-2.6 tree to linux-2.6-*
appears to have changed this git object.

git-1.4.0, Fedora Core 5.

The actual contents of the object (git-cat-file blob
0021aad5db43ccc0d0356f2f5e4e28446c8b983a) appears to be identical
however.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2006-07-30  8:30 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-30  6:27 Linux v2.6.18-rc3 Linus Torvalds
2006-07-30  8:30 ` Russell King [this message]
2006-07-31  8:02   ` Junio C Hamano
2006-07-31  4:13 ` Jesse Brandeburg
2006-07-31  4:27   ` Andrew Morton
2006-07-31 14:54     ` Alan Stern
2006-07-31 15:11       ` Andrew Morton
2006-07-31 15:59         ` Alan Stern
2006-07-31 20:34         ` Alan Stern
2006-08-02  4:31           ` Jesse Brandeburg
2006-08-02  4:59             ` Andrew Morton
2006-08-02 19:57               ` Jesse Brandeburg
2006-08-02 20:16                 ` Rafael J. Wysocki
2006-08-02 20:23                   ` Russell King
2006-08-02 20:26                     ` Rafael J. Wysocki
2006-08-02 20:32                     ` Dave Jones
2006-08-02 20:58                       ` Russell King
2006-08-02 21:01                         ` Dave Jones
2006-08-02 21:18                         ` Linus Torvalds
2006-08-02 21:38                           ` Russell King
2006-08-02 22:04                             ` Linus Torvalds
2006-08-02 22:05                             ` Russell King
2006-08-02 20:38                 ` [PATCH 1/2] SRCU: report out-of-memory errors Alan Stern
2006-08-02 20:57                   ` Paul E. McKenney
2006-08-02 20:38                 ` [PATCH 2/2] cpufreq: make the transition_notifier chain use SRCU Alan Stern
2006-08-03 15:58 ` Linux v2.6.18-rc3 Avuton Olrich
2006-08-03 16:40   ` Adrian Bunk
  -- strict thread matches above, loose matches on Subject: below --
2006-07-30 12:21 Hubert Tonneau
2006-07-30  8:43 ` Arjan van de Ven
2006-07-30  8:51 ` Greg KH
2006-07-30 11:10 ` Alistair John Strachan
2006-07-30 12:56 Hubert Tonneau
2006-07-30 13:03 Hubert Tonneau
2006-07-30  9:32 ` Jiri Slaby
2006-07-30  9:42 ` Greg KH
2006-07-30 16:05 Hubert Tonneau
2006-07-30 16:49 Hubert Tonneau
2006-07-30 17:42 Hubert Tonneau
2006-08-02 10:41 ` Takashi Iwai
2006-08-02 18:35 Hubert Tonneau
2006-08-02 14:58 ` Takashi Iwai
2006-08-04 16:37 Hubert Tonneau
2006-08-04 17:52 ` Greg KH
2006-08-04 17:55   ` Takashi Iwai

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=20060730083034.GA11360@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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