From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dan Nicolaescu Newsgroups: gmane.emacs.devel Subject: Re: VC state Date: Tue, 08 Apr 2008 20:07:40 -0700 Message-ID: <200804090307.m3937emd022768@sallyv1.ics.uci.edu> References: <200804061740.m36Hemw8021394@sallyv1.ics.uci.edu> <200804082045.m38KjG5p029421@sallyv1.ics.uci.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1207710649 12853 80.91.229.12 (9 Apr 2008 03:10:49 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 9 Apr 2008 03:10:49 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Apr 09 05:11:22 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JjQiY-0003Ug-0n for ged-emacs-devel@m.gmane.org; Wed, 09 Apr 2008 05:11:22 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JjQhu-00011A-Ai for ged-emacs-devel@m.gmane.org; Tue, 08 Apr 2008 23:10:42 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JjQhp-0000y6-1b for emacs-devel@gnu.org; Tue, 08 Apr 2008 23:10:37 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JjQhn-0000vD-9B for emacs-devel@gnu.org; Tue, 08 Apr 2008 23:10:36 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JjQhn-0000v4-0s for emacs-devel@gnu.org; Tue, 08 Apr 2008 23:10:35 -0400 Original-Received: from sallyv1.ics.uci.edu ([128.195.1.109]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60) (envelope-from ) id 1JjQhm-0002eG-IG for emacs-devel@gnu.org; Tue, 08 Apr 2008 23:10:34 -0400 X-ICS-MailScanner-Watermark: 1208315262.01407@00kLMjDgY7+Q9DnWzDSzsA Original-Received: from mothra.ics.uci.edu (mothra.ics.uci.edu [128.195.6.93]) by sallyv1.ics.uci.edu (8.13.7+Sun/8.13.7) with ESMTP id m3937emd022768; Tue, 8 Apr 2008 20:07:40 -0700 (PDT) In-Reply-To: (Stefan Monnier's message of "Tue, 08 Apr 2008 22:44:38 -0400") Original-Lines: 27 X-ICS-MailScanner: Found to be clean X-ICS-MailScanner-SpamCheck: not spam, SpamAssassin (score=-1.44, required 5, autolearn=disabled, ALL_TRUSTED -1.44) X-ICS-MailScanner-From: dann@mothra.ics.uci.edu X-detected-kernel: by monty-python.gnu.org: Solaris 10 (beta) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:94751 Archived-At: Stefan Monnier writes: > >> >> - there should be a way to operate on (sub)directories. > >> > >> > You mean something more than M-x vc-status DIR/SUBDIR RET ? > >> > >> Yes. There's sometimes an important difference between passing "src/" > >> as the argument vs passing all the files in "src/" that appear in the > >> vc-status (beside the fact that the former does not require you to > >> first mark each one of those files). > > > Many VC commands choke when given a directory parameter, so this does > > not seem particularly useful at this time. > > > More, given that vc-status is still "experimental code", and there is no > > clear path/criteria on getting it out of that state, I am not inclined > > to put more effort in adding more features to it. > > I don't see it as particularly experimental: it's what I now use as > a replacement for PCL-CVS when I use Bzr. So can the experimental label be removed then? How about binding vc-status to C-x v d so that it gets more exposure? What is the plan for vc-dired? When can it be removed? IMO it does not make sense to keep code for two different implementations of the same thing, it just adds complexity to the code.