From: Junio C Hamano <gitster@pobox.com>
To: Laszlo Papp <lpapp@kde.org>
Cc: Git List <git@vger.kernel.org>
Subject: Re: git log --follow for directories
Date: Tue, 19 May 2015 09:16:17 -0700 [thread overview]
Message-ID: <xmqqsias8rvy.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAOMwXhP-BRd356xpfdLgZ0zKYTMVryt8jtmi3T2jhVh91hY04Q@mail.gmail.com> (Laszlo Papp's message of "Tue, 19 May 2015 14:56:48 +0100")
Laszlo Papp <lpapp@kde.org> writes:
> Is there any benefit about having it like it is today or is it just
> the usual "no one has implemented it yet"?
It actually is even more sketchy than that. A single file following
was done merely as a checkbox item that works majority of the time,
and any mergy history that renames the file on one side of the side
branch but not on the other may not truly follow it.
next prev parent reply other threads:[~2015-05-19 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 13:56 git log --follow for directories Laszlo Papp
2015-05-19 16:16 ` Junio C Hamano [this message]
2015-05-20 9:20 ` Laszlo Papp
2015-05-19 23:55 ` 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=xmqqsias8rvy.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=lpapp@kde.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.