From: Andre Spiegel <spiegel@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Two question about VC.
Date: Thu, 24 Mar 2005 10:42:08 +0100 [thread overview]
Message-ID: <1111657328.2424.31.camel@localhost> (raw)
In-Reply-To: <200503240247.j2O2lve20934@raven.dms.auburn.edu>
On Wed, 2005-03-23 at 20:47 -0600, Luc Teirlinck wrote:
> 1. `(emacs)Branches' contains:
>
> Please note, however, that branches are only supported for RCS at
> the moment.
>
> I do not use branches myself, but is this really still up to date?
>
> Would the following replacement text be correct:
>
> Please note, however, that branches are not supported for SCCS.
I am not sure about MCVS, SVN, and Arch, but if we support branches for
all of them (which I tend to assume), then the replacement is correct.
> 2. (emacs)Local Version Control contains:
>
> But if you do this, the revision numbers in the RCS master no longer
> correspond to those of CVS. Technically, this is not a problem, but it
> can become difficult to keep track of what is in the CVS repository and
> what is not. So we suggest that you return from time to time to
> CVS-only operation, using `C-u C-x v v cvs <RET>'.
>
> `C-u C-x v v cvs <RET>'? Is that not going to try to commit to the
> repository? Is `C-x v b' meant?
No, C-u C-x v v cvs <RET> is indeed the intention, because committing
back to CVS is the only way to get the revision numbers consistent with
CVS again. Otherwise, you would stay on a local RCS branch that was
forked off some CVS revision in the past. That final sentence could be
clarified as:
So we suggest that you return from time to time to CVS-only operation,
committing your local changes back to the repository using 'C-u C-x v v
cvs RET'.
next prev parent reply other threads:[~2005-03-24 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 2:47 Two question about VC Luc Teirlinck
2005-03-24 9:42 ` Andre Spiegel [this message]
2005-03-25 3:27 ` Luc Teirlinck
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=1111657328.2424.31.camel@localhost \
--to=spiegel@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).