From: "Victor" <__vic@ngs.ru>
To: avarab@gmail.com
Cc: git@vger.kernel.org
Subject: Re: Strange behaviour of git log --follow
Date: Thu, 28 Mar 2019 16:32:07 +0300 [thread overview]
Message-ID: <web-54137705@mx30.intranet.ru> (raw)
In-Reply-To: <87zhpf9m10.fsf@evledraar.gmail.com>
Any plans to fix this?
On Thu, 28 Mar 2019 14:16:43 +0100
Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:
>
> On Thu, Mar 28 2019, Victor wrote:
>
>> Hello.
>>
>> $ git log include/__vic/mutex.h
>> commit 9429293f8f8fb0819c77cf1f723567f6edc8fb6a
>> Merge: 96dd9a2 f484f4e
>> Author: __vic <__vic@ngs.ru>
>> Date: 2017-12-13 10:41:32 +0300
>>
>> Merge branch 'generic' into posix
>>
>> commit f484f4e8aae32041ba56bdce12d1efd8491e94d5
>> Merge: 86b848a b9bbbe6
>> Author: __vic <__vic@ngs.ru>
>> Date: 2017-12-12 17:35:10 +0300
>>
>> waitable_event, thread, mutex
>> $ git log --follow include/__vic/mutex.h
>> $
>>
>> Why --follow makes git produce truncated history for
>>file that wasn't
>> renamed?
>>
>> My repository is available here
>> https://github.com/2underscores-vic/__vic
>
> I just briefly looked at this. It's because all changes
>to the relevant
> file are in merge commits. If you run the "log" with
>"--stat" you'll see
> no output.
>
> Something in the --follow machinery takes the same
>shortcut on merges
> and doesn't consider them.
next prev parent reply other threads:[~2019-03-28 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 12:10 Strange behaviour of git log --follow Victor
2019-03-28 13:16 ` Ævar Arnfjörð Bjarmason
2019-03-28 13:32 ` Victor [this message]
2019-03-28 13:38 ` Ævar Arnfjörð Bjarmason
-- strict thread matches above, loose matches on Subject: below --
2019-03-07 8:34 Victor
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=web-54137705@mx30.intranet.ru \
--to=__vic@ngs.ru \
--cc=avarab@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 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.