unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Two question about VC.
Date: Thu, 24 Mar 2005 21:27:26 -0600 (CST)	[thread overview]
Message-ID: <200503250327.j2P3RQO05390@raven.dms.auburn.edu> (raw)
In-Reply-To: <1111657328.2424.31.camel@localhost> (message from Andre Spiegel on Thu, 24 Mar 2005 10:42:08 +0100)

Andre Spiegel wrote:

   >   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.

In the text I am going to install occurs earlier:

+ In the following, we discuss mainly RCS, SCCS and CVS.  Nearly
+ everything said about CVS applies to Gnu Arch, Subversion and Meta-CVS
+ as well.

"Nearly" allows for the possibility of some exceptions, so complete
(well, let us hope) accuracy is only claimed for RCS, SCCS and CVS.
Short of somebody familiar with all of MCVS, SVN, and Arch carefully
going through the entire Emacs manual section on VC, I guess that we
can not do better than that.  The sentence:

   >   Please note, however, that branches are not supported for SCCS.

seems reasonably safe within that context.  Several other claims in
the Emacs section on VC only seem safe with the same qualifications.

   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'.

Thanks, that is what I am going to use.

Sincerely,

Luc.

      reply	other threads:[~2005-03-25  3:27 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
2005-03-25  3:27   ` Luc Teirlinck [this message]

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=200503250327.j2P3RQO05390@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --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).