Git development
 help / color / mirror / Atom feed
From: Marco Roeland <marco.roeland@xs4all.nl>
To: walt <w41ter@gmail.com>
Cc: git@vger.kernel.org, rmk@arm.linux.org.uk
Subject: Re: Recent annoying problem with Linus's git repository?
Date: Mon, 12 Jan 2009 08:59:42 +0100	[thread overview]
Message-ID: <20090112075942.GB29673@fiberbit.xs4all.nl> (raw)
In-Reply-To: <alpine.LNX.2.00.0901111615500.4963@x9.ybpnyarg>

On Sunday January 11th 2009 at 16:42 walt wrote:

> I've been tracking Junio's git.git and Linus's kernel.git for ages,
> and just in the last two weeks or so I've been having a recurring
> problem with the file "arch/arm/mach-integrator/clock.h" from Linus.
> 
> Any time I check out an old kernel version (e.g. during a bisect)
> and then do a "checkout master" when I'm done fiddling, git thinks
> my repository is "dirty".
> 
> This is the reason for my impurity:
> 
> # git status
> # On branch master
> # Changed but not updated:
> #   (use "git add/rm <file>..." to update what will be committed)
> #   (use "git checkout -- <file>..." to discard changes in working directory)
> #
> #       deleted:    arch/arm/mach-integrator/clock.h
> 
> It's always that same damned clock.h that remains in my working
> directory after doing the "checkout master" but it shouldn't be
> there -- it has indeed been deleted from branch master.
> 
> When I then do a "git reset --hard" I Am Purified! and no longer
> considered dirty.  But why should that extra reset step be needed?
> 
> Only that one file is involved in this recurring annoyance.  Can
> anyone figure out why, or at least reproduce the problem?

It is because commit d72fbdf01fc77628c0b837d0dd2fd564fa26ede6 "[ARM]
integrator: convert to clkdev and lookup clocks by device name" didn't
really _delete_ file arch/arm/mach-integrator/clock.h but only made it
empty. So the file still exists in the repository, but with size 0.

Cleanup scripts within the kernel build environment however always
consider empty files leftover products from the build and so delete
them.

That's why you get this result, after cleaning up.

The file should probably just be really deleted. Adding Russell to the
Cc. ;-)

At the moment (git describe gives v2.6.29-rc1-1-gae04d14) this is the
only "empty" file in the kernel repository. We've had these cases
before.
-- 
Marco Roeland

  reply	other threads:[~2009-01-12  8:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12  0:42 Recent annoying problem with Linus's git repository? walt
2009-01-12  7:59 ` Marco Roeland [this message]
2009-01-12  8:29   ` Marco Roeland

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=20090112075942.GB29673@fiberbit.xs4all.nl \
    --to=marco.roeland@xs4all.nl \
    --cc=git@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=w41ter@gmail.com \
    /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