From: Wu Zhangjin <wuzhangjin@gmail.com>
To: Shinya Kuribayashi <shinya.kuribayashi@necel.com>
Cc: yuasa@linux-mips.org, linux-mips@linux-mips.org,
linux-kernel@vger.kernel.org
Subject: Re: What's happening with vr41xx_giu.c?
Date: Fri, 10 Jul 2009 08:46:11 +0800 [thread overview]
Message-ID: <1247186771.5607.2.camel@falcon> (raw)
In-Reply-To: <4A5680B5.2090405@necel.com>
The same to me.
is there a bug in git?
On Fri, 2009-07-10 at 08:43 +0900, Shinya Kuribayashi wrote:
> Does anyone have a similar symptom?
>
> ---
> skuribay@ubuntu:linux.git$ git checkout -f master
> Already on 'master'
> skuribay@ubuntu:linux.git$
> skuribay@ubuntu:linux.git$ git log HEAD^..
> commit 4eebdebd71325d0814b1c8e093fd0d1f191da9aa
> Author: Kurt Martin <kurt@mips.com>
> Date: Wed Jul 8 19:22:35 2009 -0700
>
> MIPS: SMTC: Move cross VPE writes to after a TC is assigned to VPE.
>
> Signed-off-by: Chris Dearman <chris@mips.com>
> Signed-off-by: Raghu Gandham <raghu@mips.com>
> Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
> skuribay@ubuntu:linux.git$
> skuribay@ubuntu:linux.git$ git status
> # On branch master
> nothing to commit (working directory clean)
> skuribay@ubuntu:linux.git$
> skuribay@ubuntu:linux.git$
> 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$
>
parent reply other threads:[~2009-07-10 0:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4A5680B5.2090405@necel.com>]
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=1247186771.5607.2.camel@falcon \
--to=wuzhangjin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox