From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: emacs-devel@gnu.org
Subject: Re: State of VC?
Date: Mon, 18 Feb 2008 09:03:21 +0100 [thread overview]
Message-ID: <87y79i3d4m.fsf@ambire.localdomain> (raw)
In-Reply-To: <200802171856.m1HIuO7N000236@sallyv1.ics.uci.edu> (Dan Nicolaescu's message of "Sun, 17 Feb 2008 10:56:24 -0800")
() Dan Nicolaescu <dann@ics.uci.edu>
() Sun, 17 Feb 2008 10:56:24 -0800
AFAIK no.
I have just added vc-dir-status for Git. Sigh, moments after
the C-c C-c, i see new func vc-git--ls-files-state, which
probably could have been useful. However, before doing any
more munging, it would be nice for us to figure out what is
vc-dir-status philosophy and design, and write that down in a
vc.el comment so that backend support can derive guidance and
check for conformance. Labeling everything EXPERIMENTAL is
lame; one such warning in vc.el should suffice.
Personally, i don't think vc-directory for Git is that bad
(w/ some tweaking)[0]. I *like* the "v" prefix, non-flat
(visible) directory hierarchy, and support for RCS and CVS.
I get the feeling that vc-dir-status is simply ewoc wanking.
Perhaps a nice comment in vc.el would dispell that, hint hint.
thi
__________________________________________________________
[0] mentioned before, but there have been updates since:
http://www.gnuvola.org/wip/ (see vc-git-hacking)
next prev parent reply other threads:[~2008-02-18 8:03 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 16:43 State of VC? Eric S. Raymond
2008-01-22 17:08 ` Tom Tromey
2008-01-22 22:07 ` Dan Nicolaescu
2008-01-22 21:51 ` Tom Tromey
2008-01-23 2:31 ` Stefan Monnier
2008-01-23 19:01 ` Dan Nicolaescu
2008-01-25 0:17 ` Tom Tromey
2008-01-26 19:21 ` Dan Nicolaescu
2008-01-26 22:06 ` Eric S. Raymond
2008-02-17 18:16 ` Dan Nicolaescu
2008-02-17 18:24 ` Thien-Thi Nguyen
2008-02-17 18:56 ` Dan Nicolaescu
2008-02-18 8:03 ` Thien-Thi Nguyen [this message]
2008-02-18 8:36 ` Miles Bader
2008-02-18 8:48 ` Thien-Thi Nguyen
2008-02-18 8:57 ` Miles Bader
2008-02-18 9:18 ` Thien-Thi Nguyen
2008-02-25 15:14 ` Thien-Thi Nguyen
2008-02-18 17:40 ` Dan Nicolaescu
2008-02-19 13:52 ` Thien-Thi Nguyen
2008-02-19 15:44 ` Dan Nicolaescu
2008-02-19 16:57 ` Thien-Thi Nguyen
2008-02-19 20:53 ` Dan Nicolaescu
2008-02-17 23:09 ` Eric S. Raymond
2008-01-22 22:26 ` Glenn Morris
2008-01-23 13:01 ` Johan Bockgård
2008-01-24 7:07 ` Dan Nicolaescu
2008-01-24 8:58 ` Thien-Thi Nguyen
2008-01-24 14:57 ` Stefan Monnier
2008-01-24 15:09 ` Thien-Thi Nguyen
2008-01-25 22:47 ` Richard Stallman
2008-01-26 2:57 ` Stefan Monnier
2008-01-26 7:46 ` Alexandru Harsanyi
2008-01-24 13:23 ` Thien-Thi Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y79i3d4m.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).