From: Chris Dearman <chris@mips.com>
To: Shinya Kuribayashi <shinya.kuribayashi@necel.com>
Cc: yuasa@linux-mips.org, linux-mips@linux-mips.org
Subject: Re: What's happening with vr41xx_giu.c?
Date: Thu, 09 Jul 2009 20:07:12 -0700 [thread overview]
Message-ID: <4A56B060.7090106@mips.com> (raw)
In-Reply-To: <4A5680B5.2090405@necel.com>
Shinya Kuribayashi wrote:
> skuribay@ubuntu:linux.git$ make distclean
> skuribay@ubuntu:linux.git$
> skuribay@ubuntu:linux.git$
> skuribay@ubuntu:linux.git$ 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: drivers/char/vr41xx_giu.c
> #
> no changes added to commit (use "git add" and/or "git commit -a")
> skuribay@ubuntu:linux.git$
>
Commit 27fdd325dace4a1ebfa10e93ba6f3d25f25df674 turned
drivers/char/vr41xx_giu.c into an empty file instead of deleting it when
the file was moved to drivers/gpio
"make distclean" deletes any 0 length .c files that it finds.
Leaving drivers/char/vr41xx_giu.c as a zero length file may have been a
git bug but was probably just an oversight. I'll send a patch to clean
it up as a followup.
Chris
--
Chris Dearman
MIPS Technologies Inc 955 East Arques Ave, Sunnyvale CA 94085
next prev parent reply other threads:[~2009-07-10 3:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 23:43 What's happening with vr41xx_giu.c? Shinya Kuribayashi
2009-07-10 0:46 ` Wu Zhangjin
2009-07-10 3:07 ` Chris Dearman [this message]
2009-07-10 10:47 ` Ralf Baechle
2009-07-10 16:20 ` Junio C Hamano
2009-07-11 3:14 ` Junio C Hamano
2009-07-11 3:20 ` [PATCH 1/2] tm_to_time_t(): allow times in year 1969 Junio C Hamano
2009-07-11 3:20 ` [PATCH 2/2] apply: notice creation/removal patches produced by GNU diff Junio C Hamano
2009-07-11 3:32 ` Linus Torvalds
2009-07-11 3:57 ` Junio C Hamano
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=4A56B060.7090106@mips.com \
--to=chris@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=shinya.kuribayashi@necel.com \
--cc=yuasa@linux-mips.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.