Received: from spf5.us4.outblaze.com (spf5.us4.outblaze.com [205.158.62.27]) by sdf.lonestar.org (8.13.1/8.12.10) with ESMTP id j170djY3003571 for ; Mon, 7 Feb 2005 00:39:46 GMT Received: from lists.gnu.org (lists.gnu.org [199.232.76.165]) by spf5.us4.outblaze.com (Postfix) with ESMTP id 0118F77053 for ; Mon, 7 Feb 2005 00:40:38 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CxxA5-0003TS-UM for migo@homemail.com; Sun, 06 Feb 2005 19:53:57 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Cxx9F-0003JX-Tc for gnu-arch-users@gnu.org; Sun, 06 Feb 2005 19:53:06 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Cxx99-0003Fw-7P for gnu-arch-users@gnu.org; Sun, 06 Feb 2005 19:53:00 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Cxx97-0003CH-Cd for gnu-arch-users@gnu.org; Sun, 06 Feb 2005 19:52:57 -0500 Received: from [192.94.73.21] (helo=sdf.lonestar.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Cxwms-00075H-37 for gnu-arch-users@gnu.org; Sun, 06 Feb 2005 19:29:58 -0500 Received: from sdf.lonestar.org (IDENT:migo@ukato.freeshell.org [192.94.73.7]) by sdf.lonestar.org (8.13.1/8.12.10) with ESMTP id j170T3Ej024997; Mon, 7 Feb 2005 00:29:04 GMT Received: (from migo@localhost) by sdf.lonestar.org (8.13.1/8.12.8/Submit) id j170T3PV009610; Mon, 7 Feb 2005 00:29:03 GMT Date: Mon, 7 Feb 2005 00:29:03 +0000 From: Mikhael Goikhman To: Stefan Monnier Message-ID: <20050207002903.GA9015@ukato> Mail-Followup-To: Stefan Monnier , gnu-arch-users@gnu.org References: <20041211154916.GA1832@ukato> <20041211183809.GC3388@wisq.net> <873byasd73.fsf@tleepslib.sk.tsukuba.ac.jp> <41BDADF5.5070507@arbash-meinel.com> <20050205024050.GB26365@ukato> <20050205070604.GB18959@ukato> <877jllr4jl.fsf-monnier+gmane.comp.version-control.arch.user@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <877jllr4jl.fsf-monnier+gmane.comp.version-control.arch.user@gnu.org> User-Agent: Mutt/1.4.2.1i Cc: gnu-arch-users@gnu.org Subject: [Gnu-arch-users] File history and line annotation X-BeenThere: gnu-arch-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: a discussion list for all things arch-ish List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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: 3367 Lines: 70 On 06 Feb 2005 12:29:05 -0500, Stefan Monnier wrote: > > It may be. I also never care to "blame". Actually I don't even want to > "annotate" either. I don't really want the output that "cvs annotate" > gives me, what I want instead is to trace the live of a piece of code. Yes, pure "annotate" is of limited usefulness. Still, "tla annotate" may be done better than "cvs annotate", it may show a summary of line groups. > 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. Like this: http://arch.debian. org/cgi-bin/archzoom.cgi/schizo@debian.org--2004-zsh-upstream-cvs-head/zsh--cscvs--0--patch-3645/README?template=plain?history or this (with renames and version crossing): http://arch.debian. org/cgi-bin/archzoom.cgi/pkg-postgresql-private@lists.alioth.debian.org--2005/postgresql--no-cluster-ports-single--8.0--patch-10/postgresql8.0-8.0.0/debian/control?history I don't think it's possible to present such information clearly including hyperlinks in the command line interface. The axp tool however has such "history" command that may help to analyze a file. [Baz is likely to have such command too. However, they want to use a confusing name for it, "log", that would conflict with the term used in arch for revision log, as in `tla help | grep log` commands. I strongly oppose to this conflicting name, in favor of a more intuitive "history".] > With CVS I typically do this manually: `cvs annotate' to find the relevant > revision, then `cvs diff' to get the corresponding diff and `cvs log' to see > the corresponding message. Then if the diff is just moving the thing > around, I go back to `cvs annotate' the preceding revision, ... > It's all very inefficient for me. It's quite possible you may be more efficient with a web based interface. Or probably a GUI. Try archway 0.1.1, it should give what you need too, a history of any selected file or directory. I.e. conveniently bunched revision descriptions with operations for every revision that touched the file: to visually show changeset or log, or to get changeset or tree. > In Arch it'll be even worse because the data structure we have is not a > good match to "tla annotate". I really wish someone will write > "tla trace-code" instead of writing yet-another "tla annotate". Can you formalize such "trace-code" command, its input and output? I think what you really describe is a web based or a GUI based tool with a fast navigation in the file history, from one diff to another. Or maybe even an "annotate"-like look of the file content with an ability to remove layers (i.e. diffs) from the file. This functionality will be available in archway together with "annotate" support. Regards, Mikhael. _______________________________________________ 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/