From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Andrew Price <andy@andrewprice.me.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: once again, what's with "drivers/char/vr41xx_giu.c"?
Date: Sat, 11 Jul 2009 00:41:07 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0907110038560.25337@localhost> (raw)
In-Reply-To: <20090711013212.GA1252@sucs.org>
On Sat, 11 Jul 2009, Andrew Price wrote:
> Hi Robert,
>
> On Fri, Jul 10, 2009 at 05:06:49AM -0400, Robert P. J. Day wrote:
> >
> > on an occasional basis (after pulls), i get:
> >
> > $ git diff
> > diff --git a/drivers/char/vr41xx_giu.c b/drivers/char/vr41xx_giu.c
> > deleted file mode 100644
> > index e69de29..0000000
> > $
> >
> > not the first time i've seen that, either. methinks that file got
> > itself into a funny state.
>
> No need to panic, ...
i never panic -- i always know where my towel is.
> it just looks like somebody left an empty file without 'git rm'ing
> it. When you run 'make distclean' for example, it removes all empty
> files and leaves you with an unclean checkout. You can get the
> (empty) file back by 'git checkout'ing the file. But yes, you
> shouldn't have to. Anyway, CCing Linus to bring it to his attention.
i knew it was something like that as i recall whining about
*exactly* this happening many months ago with a different file, i just
couldn't remember the cause.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
"Kernel Newbie Corner" column @ linux.com: http://cli.gs/WG6WYX
========================================================================
prev parent reply other threads:[~2009-07-11 4:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 9:06 once again, what's with "drivers/char/vr41xx_giu.c"? Robert P. J. Day
2009-07-11 1:32 ` Andrew Price
2009-07-11 4:41 ` Robert P. J. Day [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=alpine.LFD.2.00.0907110038560.25337@localhost \
--to=rpjday@crashcourse.ca \
--cc=andy@andrewprice.me.uk \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.