Re: vc-status vs pcl-cvs

[Sam Steingold]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stefan Monnier wrote:
|> I am trying to switch from pcl-cvs to vc-status to use the same
|> interface for cvs and hg.
|
|> I have the following problems though:
|
|> 1. commit is in foreground, not background.
|
| Yes, patches welcome.
|
|> 2. there is no way to update the whole directory (O in pcl-cvs runs
|> cvs-mode-update which runs "cvs up" on the selection or the whole
|> directory).
|
| Indeed, patches welcome.

Alas, both of these run counter the current design and would require a
serious rewrite of major parts.

commit entails much work afterwards, so it has to be synchronous. ISTR
that there is a way to run a function after an asynchronous process
finishes (how?), but all backends would have to be changed to support that.

update is even worse: vc-update is _file_ oriented, it will want to
call, e.g., "hg pull -u" for _each_ file in the fileset (never mind that
the command makes sense only for the whole repository).


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIRrvLPp1Qsf2qnMcRAmxFAKCeyj7icC518bf04qsRCl57mnNMogCfTsxI
SzehN442aJluoVrSfWkNYhQ=
=o+9X
-----END PGP SIGNATURE-----