From: "Sverre Rabbelier" <alturin@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Git Mailinglist" <git@vger.kernel.org>
Subject: Re: [RFH] Finding all commits that touch the same files as a specific commit
Date: Mon, 14 Jul 2008 16:30:52 +0200 [thread overview]
Message-ID: <bd6139dc0807140730o2cdc64d0m28a83dfa72d1496b@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0807141311520.8950@racer>
On Mon, Jul 14, 2008 at 2:13 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> IMO following the file renames/code moves precisely is really worth the
> time it takes to calculate. Otherwise, the statistics will not reflect
> what was going on in the project, right?
Ah, I did not mean to imply that it is not worth the time it takes to
calculate, more that I do not know how to implement it that way. Of
course if someone has the time/motivation to do so I would very much
make use of it, but I do not have time to do so myself (at least not
until after GSoC). I can have GitStats just ignore the subtree merge
cases (and say that it is not beyond the scope of my project to take
such into account) and have a working program by the end of GSoC. But
if I spend time on getting this to work instead I might end up with a
program that does follow sub-tree merges but is only half-done, and as
such probably won't receive a "OK" grade. So, yes, I would very much
like to see this, but no time to look into doing so myself until after
GSoC.
--
Cheers,
Sverre Rabbelier
prev parent reply other threads:[~2008-07-14 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-12 15:58 [RFH] Finding all commits that touch the same files as a specific commit Sverre Rabbelier
2008-07-13 1:24 ` Junio C Hamano
2008-07-13 14:43 ` Sverre Rabbelier
2008-07-13 18:30 ` Johannes Schindelin
2008-07-14 11:17 ` Sverre Rabbelier
2008-07-14 12:13 ` Johannes Schindelin
2008-07-14 14:30 ` Sverre Rabbelier [this message]
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=bd6139dc0807140730o2cdc64d0m28a83dfa72d1496b@mail.gmail.com \
--to=alturin@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sverre@rabbelier.nl \
/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).