From: Dmitry Gutov <dgutov@yandex.ru>
To: Stefan Monnier <monnier@iro.umontreal.ca>, Eli Zaretskii <eliz@gnu.org>
Cc: oub@mat.ucm.es, emacs-devel@gnu.org
Subject: Re: RCS: (vc-next-action 1) only New Backend
Date: Mon, 21 Sep 2015 05:29:11 +0300 [thread overview]
Message-ID: <55FF6B77.7070504@yandex.ru> (raw)
In-Reply-To: <jwvd1xco6sy.fsf-monnier+emacs@gnu.org>
On 09/21/2015 05:18 AM, Stefan Monnier wrote:
> Never heard of it used for CVS (and can't find mention of it in "cvs
> commit --help"). As for SCCS, it can use that same
> log-edit-extract-headers for that.
'man cvs' has this: "-r tag is available with the commit and history
commands", which follows a paragraph devoted to "-r tag[:date]".
Overall, it doesn't seem to be that far from a common Git workflow
element: check out a branch (maybe create it) and commit to it.
If we try hard enough, maybe we could fit both new and old backends into
one VC workflow. Either split the operation likewise into two, for RCS
and friends (that would be ideal, provided it's possible; and it'll also
need a new command that allows creating a new tag/revision/branch), or
also add the ability to "check out another branch and commit" to Git and
newer backends.
next prev parent reply other threads:[~2015-09-21 2:29 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
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 [this message]
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
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=55FF6B77.7070504@yandex.ru \
--to=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--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 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).