From: Tom Tromey <tromey@redhat.com>
To: "Eric S. Raymond" <esr@snark.thyrsus.com>
Cc: emacs-devel@gnu.org
Subject: Re: State of VC?
Date: Tue, 22 Jan 2008 10:08:50 -0700 [thread overview]
Message-ID: <m3y7ahvlct.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20080122164306.3B33C83045C@snark.thyrsus.com> (Eric S. Raymond's message of "Tue\, 22 Jan 2008 11\:43\:06 -0500 \(EST\)")
>>>>> "Eric" == Eric S Raymond <esr@snark.thyrsus.com> writes:
Eric> I have time to work on VC and consider myself responsible for it
Eric> (especially since the new-VC rewrite). But I am unclear on what needs
Eric> to be done with VC at this point.
There are a few bug reports, some with patches, that were never looked
at. Reviewing those would be a good start.
Eric> Would those of you who have been hacking please summarize the
Eric> design and coding issues as you see them? From that I will try
Eric> to put together some sort of roadmap and get a start on
Eric> executing it.
This is my list for vc-status. It is roughly in order from core
pieces to UI.
* Make a new 'update' back end function to update the tree.
* Make dir-status back end function update the vc-status buffer
asynchronously. This means using a process filter.
* Don't clear vc-status buffer when updating. This means figuring out
how to insert new items into the ewoc at the right point.
* Figure out what to do about 'conflict' -- seems like it should be a
state, but none of VC seems prepared for that. There was some
discussion about this.
* Add more bindings. At least 'commit' and 'update' are needed.
In general, copy stuff from pcl-cvs or psvn.
We also need a menu and maybe a toolbar.
* Implement dir-status and update functions for all back ends.
* A few rough edges... allow multiple vc-status buffers. Decide
general approach to running the sub-process (what buffer to use,
etc; there was some traffic about this). Decide how to allow
interrupting the process. Update the vc-status buffer when a
modification is made to a buffer visiting one of the listed files.
* Whatever else that pcl-cvs does that is cool that vc-status should
have.
FWIW I am hardly working on this. I send a patch as the mood strikes.
So, don't worry too much about duplicating effort :). Dan, I think,
is leading it.
I probably forgot something.
Tom
next prev parent reply other threads:[~2008-01-22 17:08 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 [this message]
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
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=m3y7ahvlct.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=emacs-devel@gnu.org \
--cc=esr@snark.thyrsus.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 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).