Received: from spf3.us4.outblaze.com (spf3.us4.outblaze.com [205.158.62.25]) by sdf.lonestar.org (8.13.1/8.12.10) with ESMTP id j1883ZI9020261 for ; Tue, 8 Feb 2005 08:03:35 GMT Received: from hera.museatech.net (unknown [207.166.200.220]) by spf3.us4.outblaze.com (Postfix) with SMTP id 12A9F536F8 for ; Tue, 8 Feb 2005 08:04:29 +0000 (GMT) Received: (qmail 4189 invoked by uid 110); 8 Feb 2005 08:04:09 -0000 Received: from gnu-arch-dev-bounces@lists.seyza.com by hera by uid 102 with qmail-scanner-1.20 (clamscan: 0.60. spamassassin: 2.60. Clear:RC:1(127.0.0.1):. Processed in 0.033501 secs); 08 Feb 2005 08:04:09 -0000 Received: from unknown (HELO hera.museatech.net) (127.0.0.1) by hera.museatech.net with SMTP; 8 Feb 2005 08:04:09 -0000 Delivered-To: list-gnu-arch-dev@lists.seyza.com Received: (qmail 4140 invoked by uid 110); 8 Feb 2005 08:04:04 -0000 Received: from miles@lsi.nec.co.jp by hera by uid 102 with qmail-scanner-1.20 (clamscan: 0.60. spamassassin: 2.60. Clear:RC:1(207.166.200.201):. Processed in 0.028302 secs); 08 Feb 2005 08:04:04 -0000 Received: from unknown (HELO a1.mx.alal.us) (207.166.200.201) by hera.museatech.net with SMTP; 8 Feb 2005 08:04:04 -0000 Received: (qmail 15379 invoked from network); 8 Feb 2005 09:16:45 -0000 Received: from tyo202.gate.nec.co.jp (210.143.35.52) by a1.mx.alal.us with SMTP; 8 Feb 2005 09:16:42 -0000 Received: from mailgate4.nec.co.jp (mailgate54.nec.co.jp [10.7.69.195]) by tyo202.gate.nec.co.jp (8.11.7/3.7W01080315) with ESMTP id j1883qg23627; Tue, 8 Feb 2005 17:03:52 +0900 (JST) Received: (from root@localhost) by mailgate4.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id j1883kc08711; Tue, 8 Feb 2005 17:03:46 +0900 (JST) Received: from edtmg01.lsi.nec.co.jp ([10.26.16.201]) by mailsv5.nec.co.jp (8.11.7/3.7W-MAILSV4-NEC) with ESMTP id j1883jY13484; Tue, 8 Feb 2005 17:03:45 +0900 (JST) Received: from mcsss2.ucom.lsi.nec.co.jp (localhost [127.0.0.1]) by edtmg01.lsi.nec.co.jp (8.12.10/8.12.10) with ESMTP id j1883e6C011145; Tue, 8 Feb 2005 17:03:43 +0900 (JST) Received: from mctpc71 (mctpc71.ucom.lsi.nec.co.jp [10.30.118.121]) by mcsss2.ucom.lsi.nec.co.jp (8.12.10/8.12.8/EDcg v2.01-mc/1046780839) with ESMTP id j1883eKt007876; Tue, 8 Feb 2005 17:03:40 +0900 (JST) Received: by mctpc71 (Postfix, from userid 31295) id 9CD553CA; Tue, 8 Feb 2005 17:03:39 +0900 (JST) To: Anand Kumria References: <200502062235.j16MZAG0017878@xl2.seyza.com> <20050207152606.GC15171@ukato> <20050207171312.GA28689@ukato> From: Miles Bader System-Type: i686-pc-linux-gnu Blat: Foop Date: Tue, 08 Feb 2005 17:03:39 +0900 In-Reply-To: <20050207171312.GA28689@ukato> (Mikhael Goikhman's message of "Mon, 7 Feb 2005 17:13:12 +0000") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on dev.alal.com X-Spam-Level: X-Spam-Status: No, score=-1.7 required=9.0 tests=BAYES_00 autolearn=ham version=3.0.2 Cc: gnu-arch-users@gnu.org, gnu-arch-dev@lists.seyza.com Subject: [GNU-arch-dev] Re: GNU Arch status update X-BeenThere: gnu-arch-dev@lists.seyza.com X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Miles Bader List-Id: a mailing list for GNU Arch developers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: gnu-arch-dev-bounces@lists.seyza.com Errors-To: gnu-arch-dev-bounces@lists.seyza.com Status: RO X-Status: A Content-Length: 1813 Lines: 59 Mikhael Goikhman writes: > It is possible that "move" should be re-aliased from "move-id" to "mv", Yes > however I think it is good to have this complete list of 5 commands: > > add (alias: add-id) > delete (alias: delete-id) > rm (alias: remove) > mv (alias: move?, rename) > move-id (alias: move?) > > I am not sure why people think aliases are bad. cvs and svn have a lot of > them and feel no concern for this. Aliases are not what's bad; what's bad is misleading and confusing names for things. Like the current definitions of "move" and "delete" in tla. A less confusing set of commmands would be: rm (alias: remove?) mv (alias: move, rename) add-id (alias: add) delete-id move-id As a matter of presentation, one can advertise "add" and "add-id" as separate commands, even though they really do the same thing -- one being for users, the other for scripts or something. Then: add rm (alias: remove?) mv (alias: move, rename) add-id delete-id move-id For more consistency, it might be better to use "remove-id" instead of "delete-id"; remove-id also seems slightly more accurate, in that "remove-id" seems to emphasize the fact that you're removing the id from _something_ (a file), whereas "delete-id" sounds like it's just removing a particular id from the global pool of ids; one might expect a "remove-id" command to take an id as an argument instead of a filename. So: add rm (alias: remove?) mv (alias: move, rename) add-id remove-id move-id -Miles -- 97% of everything is grunge _______________________________________________ Gnu-arch-dev mailing list Gnu-arch-dev@lists.seyza.com http://lists.seyza.com/cgi-bin/mailman/listinfo/gnu-arch-dev