From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: oub@mat.ucm.es, dgutov@yandex.ru, emacs-devel@gnu.org
Subject: Re: RCS: (vc-next-action 1) only New Backend
Date: Sun, 20 Sep 2015 22:40:52 +0300 [thread overview]
Message-ID: <83wpvkop4r.fsf@gnu.org> (raw)
In-Reply-To: <jwva8sgq4ma.fsf-monnier+emacs@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: oub@mat.ucm.es, emacs-devel@gnu.org, dgutov@yandex.ru
> Date: Sun, 20 Sep 2015 15:25:21 -0400
>
> > And, btw, the removal of the capability to specify a revision didn't
> > remove the prefix argument, it just limited its meaning to specifying
> > a different back-end.
>
> That's the point: it leaves the C-u to be used for something else which
> is not useful only for RCS but potentially for all backends.
>
> I'm perfectly OK with providing the ability to specify the revision
> number to use (in vc-rcs.el). What I'm opposed to is to add special
> support for that in the generic code. It can all be done within
> vc-rcs.el using log-edit-extract-headers.
Once again, specifying a revision at check-in time is not limited to
RCS, it is also supported by CVS and SCCS.
next prev parent reply other threads:[~2015-09-20 19:40 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 15:39 RCS: (vc-next-action 1) only New Backend Uwe Brauer
2015-09-18 17:18 ` Eli Zaretskii
2015-09-18 20:46 ` Uwe Brauer
2015-09-19 7:00 ` Eli Zaretskii
2015-09-19 8:46 ` Uwe Brauer
2015-09-19 8:59 ` David Kastrup
2015-09-19 9:23 ` Eli Zaretskii
2015-09-19 9:36 ` Uwe Brauer
2015-09-19 10:34 ` Eli Zaretskii
2015-09-19 9:30 ` Eli Zaretskii
2015-09-19 10:00 ` David Kastrup
2015-09-19 10:30 ` Uwe Brauer
2015-09-19 10:40 ` Eli Zaretskii
2015-09-19 10:58 ` David Kastrup
2015-09-19 11:06 ` Eli Zaretskii
2015-09-19 12:29 ` Uwe Brauer
2015-09-19 14:11 ` Eli Zaretskii
2015-09-19 21:15 ` Uwe Brauer
2015-09-19 16:05 ` Dmitry Gutov
2015-09-19 17:35 ` Eli Zaretskii
2015-09-19 17:41 ` Dmitry Gutov
2015-09-19 17:49 ` Eli Zaretskii
2015-09-19 19:44 ` Dmitry Gutov
2015-09-19 21:14 ` Uwe Brauer
2015-09-19 22:42 ` Dmitry Gutov
2015-09-20 6:08 ` Eli Zaretskii
2015-09-20 13:10 ` Dmitry Gutov
2015-09-20 14:49 ` Eli Zaretskii
2015-09-20 16:27 ` Stefan Monnier
2015-09-20 17:10 ` Eli Zaretskii
2015-09-20 17:15 ` Eli Zaretskii
2015-09-20 19:25 ` Stefan Monnier
2015-09-20 19:40 ` Eli Zaretskii [this message]
2015-09-20 20:53 ` Dmitry Gutov
2015-09-21 6:17 ` Eli Zaretskii
2015-09-21 2:18 ` Stefan Monnier
2015-09-21 2:29 ` Dmitry Gutov
2015-09-21 6:59 ` Eli Zaretskii
2015-09-21 14:06 ` Dmitry Gutov
2015-09-21 16:12 ` Eli Zaretskii
2015-09-21 16:48 ` Dmitry Gutov
2015-09-21 16:59 ` Eli Zaretskii
2015-09-21 17:33 ` Dmitry Gutov
2015-09-21 19:21 ` Eli Zaretskii
2015-09-21 5:30 ` David Kastrup
2015-09-21 13:14 ` Stefan Monnier
2015-09-21 7:08 ` Eli Zaretskii
2015-09-20 23:54 ` Dmitry Gutov
2015-09-21 6:52 ` Eli Zaretskii
2015-09-20 6:03 ` Eli Zaretskii
2015-09-19 20:21 ` Stefan Monnier
2015-09-19 9:31 ` Uwe Brauer
2015-09-19 17:29 ` Stefan Monnier
2015-09-19 17:45 ` Eli Zaretskii
2015-09-19 20:18 ` Stefan Monnier
2015-09-20 6:06 ` Eli Zaretskii
2015-09-19 9:21 ` Eli Zaretskii
2015-09-19 9:35 ` Uwe Brauer
2015-09-19 10:34 ` Eli Zaretskii
2015-09-19 10:35 ` Uwe Brauer
2015-09-20 10:05 ` Uwe Brauer
2015-09-20 10:45 ` Eli Zaretskii
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=83wpvkop4r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=oub@mat.ucm.es \
/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.