From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel,gmane.comp.version-control.arch.user Subject: Re: cvs <-> arch mirroring scripts Date: Tue, 19 Aug 2003 22:43:19 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <1060744673.2522.27.camel@columbia> <1060803518.28891.27.camel@columbia> <20030818222912.GC6940@fencepost> Reply-To: rms@gnu.org NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1061358427 4221 80.91.224.253 (20 Aug 2003 05:47:07 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 20 Aug 2003 05:47:07 +0000 (UTC) Cc: gnu-arch-users@gnu.org, emacs-devel@gnu.org, miles@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Wed Aug 20 07:47:05 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19pLoH-0008S4-00 for ; Wed, 20 Aug 2003 07:47:05 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 19pLrP-0008LB-00 for ; Wed, 20 Aug 2003 07:50:20 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.20) id 19pKhd-0005C2-Jr for emacs-devel@quimby.gnus.org; Wed, 20 Aug 2003 00:36:09 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20) id 19pK7B-0001kZ-NZ for emacs-devel@gnu.org; Tue, 19 Aug 2003 23:58:29 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20) id 19pJvN-00065J-Sd for emacs-devel@gnu.org; Tue, 19 Aug 2003 23:46:49 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.20) id 19pJAr-0001uS-69; Tue, 19 Aug 2003 22:58:13 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.20) id 19pIwR-00086P-Od; Tue, 19 Aug 2003 22:43:19 -0400 Original-To: Miles Bader In-reply-to: <20030818222912.GC6940@fencepost> (message from Miles Bader on Mon, 18 Aug 2003 18:29:12 -0400) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:16026 gmane.comp.version-control.arch.user:3302 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:16026 > How is that useful to CVS users like me? Because (1) it identifies which arch revision the change came from, which allows you to go back to the arch changeset to get more info if you need it, (2) it helps identify the change as part of a changeset along with other files, which is a generally useful concept even if not supported by the mechanics of CVS. That's not particularly useful for me. You may not immediately need this info in your everyday log browsing, but that doesnt mean it's not useful. However, it does suggest that maybe the idea of adding output-filtering to vc.el's C-v l command is good. That way you can strip out this stuff that may interfere with casual browsing, but it's available in case you ever _do_ want it. Ok, let's try to do it that way. > 1. We should think of this person as the one who checked in the > change. If so, the info is useful but the CVS checkin user info is > useless. This name should go in the CVS checkin user name, not in a > separate "Creator" field. This is true. I think modifying the `cvs' client to do such a substitution would be a pain, but maybe this is another thing that vc.el could easily do. Ok. [Also note that this field could be used in other non-arch-related cases, when for some reason one person checks in a change for another] That would be inconsistent. If in arch changes the person in the Creator field is considered the one who checked in the change, then we should not use the Creator field to indicate the real author in other cases. Currently what we do is put the real author in ChangeLog, not in the CVS log entry. That seems to work well and I see no reason to change it.