From: "Eric S. Raymond" <esr@thyrsus.com>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: Tom Tromey <tromey@redhat.com>,
"Eric S. Raymond" <esr@snark.thyrsus.com>,
emacs-devel@gnu.org
Subject: Re: State of VC?
Date: Sun, 17 Feb 2008 18:09:52 -0500 [thread overview]
Message-ID: <20080217230952.GA2077@thyrsus.com> (raw)
In-Reply-To: <200802171816.m1HIGmZr015446@sallyv1.ics.uci.edu>
Dan Nicolaescu <dann@ics.uci.edu>:
> "Eric S. Raymond" <esr@thyrsus.com> writes:
>
> > Dan Nicolaescu <dann@ics.uci.edu>:
> > > But maybe first we should wait for ESR to post his plan/roadmap before
> > > doing any further changes. Hopefully this will happen soon ...
> >
> > Sorry about the delay; we're prepping for a release on another project
> > of mine at the moment. I should be able to get to this Tuesday or Wednesday.
>
> Any news about this?
>
> IMO the most pressing need right now is to move vc-status from it's
> state of limbo.
>
> Given how simple the vc-status code is, how easy it is to extend, and
> how long it took for fundamental problems in vc-dired to be fixed, it's
> quite easy to conclude that vc-status is the best way to go forward.
Sorry, I've been heads-down on another project. Actually it's Battle For
Wesnoth, the one I've held up as a tool-use model here. We're heading
towards a major stable 1.4 release and, as I'm one of the core devs, this
involves a huge amount of work.
I'll get back to working on VC probably around the first week of
March, possibly earlier. In the meantime, anybody who wants to take the
initiative on moving VC to use vc-status sooner has my approval and
encouragement to do it.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2008-02-17 23:09 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080217230952.GA2077@thyrsus.com \
--to=esr@thyrsus.com \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=esr@snark.thyrsus.com \
--cc=tromey@redhat.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.