public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Shawn Pearce <spearce@spearce•org>
To: git@vger•kernel.org
Subject: Modified files coming from v2.6.12 checkout
Date: Wed, 15 Feb 2006 15:04:42 -0500	[thread overview]
Message-ID: <20060215200442.GB5742@spearce.org> (raw)

I'm trying to do a performance test suggested by Catalin. I cloned
(what I thought to be) Linus public kernel tree[1] then locally
cloned it again and tried to checkout a working directory of v2.6.12:

  $ git-clone [1]
  $ git-clone -l -n linux-2.6 bigmergetest
  $ cd bigmergetest
  $ ls -a
  .       ..      .git
  $ git-update-ref HEAD $(git-rev-parse --verify v2.6.12^{commit})
  $ git-read-tree HEAD
  $ git-checkout-index -u -a
  git-checkout-index: include/linux/netfilter_ipv4/ipt_connmark.h already exists
  ...
  git-checkout-index: net/ipv4/netfilter/ipt_tos.c already exists
  git-checkout-index: net/ipv6/netfilter/ip6t_mark.c already exists

That can't be right.  Why do so many files already exist during
an empty checkout? git-status is reporting these files as being
modified.  If I commit these 'modified' files there's actually a
rather large delta if I diff v2.6.12 and the new commit.

I've tried this both with git 1.1.4 and 1.2.0.  Same result.
I've also tried it with both the v2.6.12 tag and the current HEAD.
Same result just different files having the problem.

I just looked at the linux-2.6 directory which I cloned from [1];
it appears to have the same problem but on a slightly different
set of files than the v.2.6.12 clone:

  $ git-status | grep modified | wc -l
       18

Thoughts?  Suggestions of where to start looking for a fault?
Does the fault exist between the chair and the keyboard?


[1] http://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git/

-- 
Shawn.

next             reply	other threads:[~2006-02-15 20:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-15 20:04 Shawn Pearce [this message]
2006-02-15 20:21 ` Modified files coming from v2.6.12 checkout Shawn Pearce

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=20060215200442.GB5742@spearce.org \
    --to=spearce@spearce$(echo .)org \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox