From: Martin Langhoff <martin.langhoff@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jeff King <peff@peff.net>,
Albert Krawczyk <albert@burgmann.anu.edu.au>,
git@vger.kernel.org
Subject: Re: Git log follow question
Date: Fri, 14 May 2010 11:19:39 -0400 [thread overview]
Message-ID: <AANLkTimfuINt0v_SETz9NsMGVXDL9d150B8En4TKqw3b@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1005140730030.3711@i5.linux-foundation.org>
On Fri, May 14, 2010 at 10:50 AM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> If we want --follow and --parent to work together, you'd need to move the
> special rename hack to be in the early phases. I'm sure it's possible. It
> might even be reasonably simple. But it's very fundamentally not what we
> do now.
...
> It would
> be nice if "gitk --follow <pathname>" worked properly, but it's just not
> something I care very much about.
Putting the internal machinery aside, it would be enormously useful
for the end user.
The Linux kernel is unusual in that there are relatively few renames /
reorgs in the mainline -- maintainers pushback and force those things
to happen before a patchset is merged. And you (as the lead
maintainer) probably know all the renames in your own project.
The use case for this is: "Where the hell does this WTF-worthy
function come from, in this WTF-esque old codebase I just inherited?"
cheers,
m
--
martin.langhoff@gmail.com
martin@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
next prev parent reply other threads:[~2010-05-14 15:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 0:57 Git log follow question Albert Krawczyk
2010-05-14 4:16 ` Bo Yang
2010-05-14 4:37 ` Jeff King
2010-05-14 14:50 ` Linus Torvalds
2010-05-14 15:19 ` Martin Langhoff [this message]
2010-05-14 15:29 ` Linus Torvalds
[not found] ` <22729_1273851106_4BED6CE2_22729_6897_1_alpine.LFD.2.00.1005140827250.3711@i5.linux-foundation.org>
2010-05-14 22:39 ` Albert Krawczyk
2010-05-25 9:31 ` Jeff King
2010-05-25 18:49 ` Linus Torvalds
2010-05-26 5:58 ` Jeff King
2010-05-26 14:40 ` Linus Torvalds
[not found] ` <21464_1273811837_4BECD37D_21464_745_1_20100514043704.GC6075@coredump.intra.peff.net>
2010-05-14 4:43 ` Albert Krawczyk
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=AANLkTimfuINt0v_SETz9NsMGVXDL9d150B8En4TKqw3b@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=albert@burgmann.anu.edu.au \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=torvalds@linux-foundation.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).