From: Fredrik Kuivinen <freku045@student.liu.se>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Libify puzzle
Date: Tue, 7 Mar 2006 16:40:26 +0100 [thread overview]
Message-ID: <20060307154026.GA4457@c165.ib.student.liu.se> (raw)
In-Reply-To: <Pine.LNX.4.63.0603071151520.14200@wbgn013.biozentrum.uni-wuerzburg.de>
On Tue, Mar 07, 2006 at 12:00:02PM +0100, Johannes Schindelin wrote:
> Hi,
>
> I was just thinking a bit about teaching git-blame about renames, and hit
> a problem: When rev-list stops because none of the parents has the file of
> interest, the program should look if the parents contained a similar file
> which got deleted. But the commit's parents were explicitely culled!
>
> The problem seems to affect more programs when we try to libify them: What
> used to be a pipe between two programs, can no longer just set
> save_commit_buffer = 0 in the first stage, since the second might depend
> on the buffer.
>
> Would the correct solution be something like reparse_commit(commit)?
>
I have started on the rename support for git-blame but it isn't
working code yet.
My idea is to change the revision.h interface a bit. Instead having
the pathname pruning hard-coded in try_to_simplify_commit as it is
today we could have a pointer to a function in the rev_info structure
which is called the same way as try_to_simplify_commit is called
now. Then users of the revision walking interface could populate the
rev_info structure with their own try_to_simplify_commit-like
function. In the case of git-blame that function could then do the
appropriate rename detection.
Thoughts/comments?
- Fredrik
prev parent reply other threads:[~2006-03-07 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 11:00 Libify puzzle Johannes Schindelin
2006-03-07 15:40 ` Fredrik Kuivinen [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=20060307154026.GA4457@c165.ib.student.liu.se \
--to=freku045@student.liu.se \
--cc=Johannes.Schindelin@gmx.de \
--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).