git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Anatol Pomozov" <anatol.pomozov@gmail.com>
To: git@vger.kernel.org
Subject: Incorrect git-blame result if I use full path to file
Date: Sun, 2 Dec 2007 16:52:36 -0800	[thread overview]
Message-ID: <3665a1a00712021652tbdfe9d1tdc4575d225bfed36@mail.gmail.com> (raw)

Hi, all.

I just start learning git and I found a bug (but sorry if the
functionality I am trying to blame as a bug not actually bug and it
was made by intention)

The problem is that git-blame returns incorrect result if you use full
path for files.

Here is an example script that generates repo.

#go to empty dir
git init
echo "On master" >> master.txt
git add master.txt
git commit -m "First commit"
echo "On master" >> master.txt
git commit -a -m "Second commit"
echo "On master" >> master.txt


Now lets do blame for master.txt
anatol:repo $ git blame master.txt
^69bce74 (Anatol Pomozov    2007-12-02 16:44:07 -0800 1) On master
4e2bbde4 (Anatol Pomozov    2007-12-02 16:44:15 -0800 2) On master
00000000 (Not Committed Yet 2007-12-02 16:44:27 -0800 3) On master

It is exaclty what we expect. But lets try full path for master.txt
$pwd
/personal/sources/learn/gitea/repo
$git blame /personal/sources/learn/gitea/repo/master.txt
^69bce74 (Anatol Pomozov 2007-12-02 16:44:07 -0800 1) On master
^69bce74 (Anatol Pomozov 2007-12-02 16:44:07 -0800 2) On master
^69bce74 (Anatol Pomozov 2007-12-02 16:44:07 -0800 3) On master


Now git shows that all lines in the file were changed by the first
commit and that it does not true.

-- 
anatol

             reply	other threads:[~2007-12-03  0:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-03  0:52 Anatol Pomozov [this message]
2007-12-03  2:19 ` Incorrect git-blame result if I use full path to file Junio C Hamano
2007-12-03  2:28   ` Jeff King
2007-12-03 17:26   ` Linus Torvalds
2007-12-03 18:09     ` Johannes Schindelin
2007-12-03 18:13       ` Linus Torvalds
2007-12-03 18:19         ` Linus Torvalds
2007-12-03  2:27 ` Jeff King
2007-12-03  2:40   ` Junio C Hamano
2007-12-03  2:49     ` Jeff King
2007-12-03  6:55       ` Robin Rosenberg
2007-12-03 20:53         ` [PATCH] Make Git accept absolute path names for files within the work tree Robin Rosenberg
2007-12-03 23:03           ` Junio C Hamano
2007-12-04  1:43           ` Jeff King
2007-12-04  2:17             ` Johannes Schindelin
2007-12-04  6:42               ` Robin Rosenberg
2007-12-04 11:50                 ` Johannes Schindelin
2007-12-04 15:59                   ` Linus Torvalds
2007-12-04 22:08                     ` Jeff King
2007-12-04 22:52                       ` Linus Torvalds
2007-12-06  6:12                         ` Jeff King

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=3665a1a00712021652tbdfe9d1tdc4575d225bfed36@mail.gmail.com \
    --to=anatol.pomozov@gmail.com \
    --cc=git@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).