From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: RCS: (vc-next-action 1) only New Backend Date: Mon, 21 Sep 2015 09:59:55 +0300 Message-ID: <83pp1cntp0.fsf@gnu.org> References: <87mvwjohyi.fsf@mat.ucm.es> <837fnmrizs.fsf@gnu.org> <877fnm4wzn.fsf@mat.ucm.es> <876136lr83.fsf@fencepost.gnu.org> <83y4g2pxh3.fsf@gnu.org> <871tdulodu.fsf@fencepost.gnu.org> <83twqqpu91.fsf@gnu.org> <55FD87DE.3030506@yandex.ru> <83pp1epb17.fsf@gnu.org> <55FD9E4D.8080909@yandex.ru> <83lhc2pae8.fsf@gnu.org> <55FDBB3B.1070706@yandex.ru> <878u82ru1j.fsf@mat.ucm.es> <83h9mppqqn.fsf@gnu.org> <55FEB04C.4090205@yandex.ru> <83a8shp2n3.fsf@gnu.org> <8337y9ow3v.fsf@gnu.org> <831tdtovv3.fsf@gnu.org> <83wpvkop4r.fsf@gnu.org> <55FF6B77.7070504@yandex.ru> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1442818865 11817 80.91.229.3 (21 Sep 2015 07:01:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 21 Sep 2015 07:01:05 +0000 (UTC) Cc: oub@mat.ucm.es, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 21 09:00:51 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Zdv5l-0003xl-BW for ged-emacs-devel@m.gmane.org; Mon, 21 Sep 2015 09:00:49 +0200 Original-Received: from localhost ([::1]:56155 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zdv5k-0005VF-TJ for ged-emacs-devel@m.gmane.org; Mon, 21 Sep 2015 03:00:48 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33970) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zdv5S-0005Ut-0V for emacs-devel@gnu.org; Mon, 21 Sep 2015 03:00:30 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zdv5O-0004fz-Q9 for emacs-devel@gnu.org; Mon, 21 Sep 2015 03:00:29 -0400 Original-Received: from mtaout27.012.net.il ([80.179.55.183]:38423) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zdv5O-0004fQ-Cr for emacs-devel@gnu.org; Mon, 21 Sep 2015 03:00:26 -0400 Original-Received: from conversion-daemon.mtaout27.012.net.il by mtaout27.012.net.il (HyperSendmail v2007.08) id <0NV000H00LX73800@mtaout27.012.net.il> for emacs-devel@gnu.org; Mon, 21 Sep 2015 09:56:10 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([84.94.185.246]) by mtaout27.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NV000CT7LXMET40@mtaout27.012.net.il>; Mon, 21 Sep 2015 09:56:10 +0300 (IDT) In-reply-to: <55FF6B77.7070504@yandex.ru> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.183 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:190173 Archived-At: > Cc: oub@mat.ucm.es, emacs-devel@gnu.org > From: Dmitry Gutov > Date: Mon, 21 Sep 2015 05:29:11 +0300 > > 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]". No, that's the wrong command. We are talking about "cvs commit". The CVS manual has this text: commit options -------------- [...] `-r REVISION' Commit to REVISION. REVISION must be either a branch, or a revision on the main trunk that is higher than any existing revision number (*note Assigning revisions::). You cannot commit to a specific revision on a branch. > 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. I think another possibility is to commit a tag with the specified REVISION string immediately after committing the current changeset.