From: Stefan Monnier <monnier@iro.umontreal.ca>
To: esr@snark.thyrsus.com (Eric S. Raymond)
Cc: emacs-devel@gnu.org
Subject: Re: Request for policy ruling - dropping Arch support fom VC?
Date: Fri, 05 Dec 2014 23:53:02 -0500 [thread overview]
Message-ID: <jwvwq655qpy.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20141205231217.B9D6F383525@snark.thyrsus.com> (Eric S. Raymond's message of "Fri, 5 Dec 2014 18:12:17 -0500 (EST)")
> I don't know what the project policy is on supporting modes for
> software that has been end-of-lifed. Now I need to know.
As usual the answer is "it depends". I was planning to move vc-arch.el
to the lisp/obsolete subdirectory, but as for dropping support outright,
I'm not completely sure because I don't know if some project might still be
using Arch or not.
> Michael Albinus has been working on a test framework for VC. In the
> process, we've discovered that the Arch register method is busted.
> I'm pretty sure I didn't do this with my recent changes to VC, that
> the arch backend had bitrotted due to changes in Arch.
It should be pretty easy to check if Emacs-24.4's vc-arch.el works right.
I suggest to keep vc-arch.el on life-support with minimal efforts: only
update the code "in the obvious way", just so that if someone were to
come and complain that Arch doesn't work any more, it should be
reasonably easy to fix it.
Stefan
next prev parent reply other threads:[~2014-12-06 4:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 23:12 Request for policy ruling - dropping Arch support fom VC? Eric S. Raymond
2014-12-06 2:07 ` Paul Eggert
2014-12-06 4:53 ` Stefan Monnier [this message]
2014-12-06 6:05 ` Eric S. Raymond
2014-12-06 9:16 ` Ulrich Mueller
2014-12-06 10:07 ` Eric S. Raymond
2014-12-06 13:40 ` Ulrich Mueller
2014-12-06 13:51 ` Eric S. Raymond
2014-12-06 22:50 ` Stefan Monnier
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=jwvwq655qpy.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--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 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.