To: gnu-arch-users@gnu.org
From: Stefan Monnier <monnier@iro.umontreal.ca>
Date: Sun, 06 Feb 2005 20:09:03 -0500
Message-ID: <87fz09npy5.fsf-monnier+gmane.comp.version-control.arch.user@gnu.org>
References: <20041211154916.GA1832@ukato> <20041211183809.GC3388@wisq.net>
	<873byasd73.fsf@tleepslib.sk.tsukuba.ac.jp>
	<cpk7vo$gu8$1@sea.gmane.org> <41BDADF5.5070507@arbash-meinel.com>
	<buo1xbwsxhi.fsf@mctpc71.ucom.lsi.nec.co.jp>
	<20050205024050.GB26365@ukato>
	<fc339e4a05020420383dab9f7d@mail.gmail.com>
	<20050205070604.GB18959@ukato>
	<877jllr4jl.fsf-monnier+gmane.comp.version-control.arch.user@gnu.org>
	<20050207002903.GA9015@ukato>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/21.3.50 (gnu/linux)
Cancel-Lock: sha1:LZmmZIBx0lF33mSWmqtwdR4V7Gw=
Subject: [Gnu-arch-users] Re: File history and line annotation
Precedence: list
Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Status: RO
Content-Length: 1735
Lines: 34
>> I.e. from a set of code lines, I want to see all the diff+log that resulted
>> in those lines.  Also, often enough the diff+log is not what I want because
>> it just corresponds to a re-indent or a move, so I often also want to see
>> the parents of those diffs (i.e. the diff+log that resulted in the text that
>> was then changed by those diffs), their parents's parents, ...
>> until I really find the diff+log where the code was originally added.

> It seems that you speak about the complete file history.

No: only the part that affects some set of code lines.

> It's quite possible you may be more efficient with a web based interface.

I'm interested in a command-line tool on top of which a web-based (or
rather Emacs-based ;-) interface can be built.

> Can you formalize such "trace-code" command, its input and output?

It could look like:

   tla trace-code FILE FROM TO REV

and return all the diff+log that together result in lines FROM..TO of
revision REV of file FILE.  Hopefully the output would be written in such
a way that it is easy to mechanically extract further "FROM TO REV" triplets
in order to call the command again to get the trace-code explaining how the
code modified by one of the diff+log ended up the way it is and thus work
your way back in the history of the relevant piece of code through
reindentations, moves, typos, ... until you get to the actual meat
(typically the one or two diff+log that really introduced the piece of code
you're wondering about).


        Stefan


_______________________________________________
Gnu-arch-users mailing list
Gnu-arch-users@gnu.org
http://lists.gnu.org/mailman/listinfo/gnu-arch-users

GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/