From: Ivan Shmakov <ivan@siamics.net>
To: emacs-devel@gnu.org
Subject: Re: My plans for VC mode
Date: Sun, 23 Nov 2014 19:27:51 +0000 [thread overview]
Message-ID: <87k32lu37s.fsf@violet.siamics.net> (raw)
In-Reply-To: <20141122164134.GD25909@thyrsus.com> (Eric S. Raymond's message of "Sat, 22 Nov 2014 11:41:34 -0500")
>>>>> Eric S Raymond <esr@thyrsus.com> writes:
>>>>> Stefan Monnier <monnier@IRO.UMontreal.CA>:
>> I'm fine with breaking backward compatibility. But then please try
>> to find "all" the out-of-tree backends for Free revision control
>> systems, and then try to find their maintainer to get them in the
>> loop.
> I'd be happy to get the maintainers involved, but I don't have any
> idea how to go about finding the out-of-tree back ends. Help would
> be appreciated.
FWIW, as a maintainer of vc-mw.el, I’m already following this
thread (albeit loosely.)
Sure, I’m all for simplifying the VC-to-backend interface, yet
I’m somewhat concerned over whether I’d be able to provide
support for /both/ Emacs 24 and the Git ‘master’ in my code.
At the very least, I hope that the calling conventions for the
most basic interface functions my backend provides (including
registered, state, working-revision, find-revision, checkin,
print-log) are changed in a kind of a compatible way. (For
instance, I could easily make ‘state’ also accept a list of
files instead of just a single one. Or so I hope, anyway.)
Otherwise, I’d rather appreciate if the updated interface could
use some entirely new function names where the semantics changes
drastically, so that I can provide functions implementing both
the old and the new interface. (I do not think it’s necessary
for the new VC to support the old interface in this case.)
[…]
--
FSF associate member #7257 http://boycottsystemd.org/ … 3013 B6A0 230E 334A
next prev parent reply other threads:[~2014-11-23 19:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-22 13:33 My plans for VC mode Unknown
2014-11-22 14:17 ` Jan D.
2014-11-22 16:29 ` Eric S. Raymond
2014-11-22 16:44 ` Jan D.
2014-11-22 14:33 ` Dmitry Gutov
2014-11-22 16:37 ` Eric S. Raymond
2014-11-22 17:46 ` Dmitry Gutov
2014-11-22 18:08 ` Eric S. Raymond
2014-11-23 1:27 ` Dmitry Gutov
2014-11-22 22:32 ` Stefan Monnier
2014-11-23 1:01 ` Dmitry Gutov
2014-11-23 6:25 ` Eric S. Raymond
2014-11-22 23:17 ` Steinar Bang
2014-11-23 20:02 ` Eric S. Raymond
2014-11-23 20:11 ` Eli Zaretskii
2014-11-22 16:11 ` Stefan Monnier
2014-11-22 16:41 ` Eric S. Raymond
2014-11-22 16:59 ` Dieter Deyke
2014-11-22 22:34 ` Stefan Monnier
2014-11-23 19:58 ` Eric S. Raymond
2014-11-24 6:40 ` Dieter Deyke
2014-11-24 7:50 ` Eric S. Raymond
2014-11-24 7:55 ` Kan-Ru Chen (陳侃如)
2014-11-24 8:07 ` Eric S. Raymond
2014-11-24 14:33 ` Stefan Monnier
2014-11-24 17:57 ` Eric S. Raymond
2014-11-23 19:27 ` Ivan Shmakov [this message]
2014-11-23 20:10 ` Eric S. Raymond
2014-11-22 19:02 ` Michael Albinus
2014-11-23 6:26 ` Eric S. Raymond
2014-11-23 8:23 ` Michael Albinus
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=87k32lu37s.fsf@violet.siamics.net \
--to=ivan@siamics.net \
--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 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.