All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Zorro Lang <zlang@redhat.com>
Cc: guaneryu@gmail.com, fstests@vger.kernel.org
Subject: Re: Is there something wrong about the commit log of tools/nextid ?
Date: Tue, 27 Mar 2018 09:32:26 -0700	[thread overview]
Message-ID: <20180327163226.GA11581@magnolia> (raw)
In-Reply-To: <20180327101531.GL4684@dhcp12-143.nay.redhat.com>

On Tue, Mar 27, 2018 at 06:15:31PM +0800, Zorro Lang wrote:
> Hi,
> 
> Recently I always find this message when I do:
> 
> # git status
> On branch master                               
> Your branch is up-to-date with 'origin/master'.                                                
> 
> Changes not staged for commit:                 
>   (use "git add <file>..." to update what will be committed)                                   
>   (use "git checkout -- <file>..." to discard changes in working directory)                    
> 
>         typechange: tools/nextid
> 
> Even git pull to latest commit, this problem is still there.
> If I did `git blame tools/nextid`, I can't see the commit message
> about this file. If I did `git checkout -- tools/nextid`, then
> `git blame tools/nextid` shows:
> 
>   208422233 (Darrick J. Wong 2015-12-21 18:07:52 +1100 1) sort-group
> 
> Only this one line. I don't know what happened to this file, is there
> something wrong when merge or push it?

It's supposed to be a symbolic link, hence the one-line git blame after
you git checkout.

--D

> Thanks,
> Zorro
> --
> To unsubscribe from this list: send the line "unsubscribe fstests" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2018-03-27 16:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-27 10:15 Is there something wrong about the commit log of tools/nextid ? Zorro Lang
2018-03-27 16:32 ` Darrick J. Wong [this message]
2018-03-28  2:12   ` Zorro Lang

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=20180327163226.GA11581@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=fstests@vger.kernel.org \
    --cc=guaneryu@gmail.com \
    --cc=zlang@redhat.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 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.