From: Dan Nicolaescu <dann@ics.uci.edu>
To: tomas@tuxteam.de
Cc: "Stephen J. Turnbull" <stephen@xemacs.org>,
Chong Yidong <cyd@stupidchicken.com>,
emacs-devel@gnu.org
Subject: Re: moving SCCS later in vc-handled-backends
Date: Wed, 24 Jun 2009 07:58:09 -0700 (PDT) [thread overview]
Message-ID: <200906241458.n5OEw9ND002207@godzilla.ics.uci.edu> (raw)
In-Reply-To: <20090624075137.GB13630@tomas> (tomas@tuxteam.de's message of "Wed, 24 Jun 2009 09:51:37 +0200")
tomas@tuxteam.de writes:
> I have to concur with Stephen here. *If* someone is using SCCS with an
> odd file managed by RCS, it'd be better having the SCCS commit fail
> loudly (and leading the user to investigate the cause) than the RCS
> commit failing (nearly) silently, leading possibly to a botched backup
> much further down the time line.
Can you please describe precisely the scenario that you have in mind?
Because the above is not a problem.
It is not possible to commit at the same time files that are managed by
different backends.
More, the relative order of RCS and SCCS stays the same, so the behavior
for RCS and SCCS stays the same.
> Note that I'm no user of RCS, much less of SCCS, so take this with the
> appropriate two fists of salt.
next prev parent reply other threads:[~2009-06-24 14:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 7:01 moving SCCS later in vc-handled-backends Dan Nicolaescu
2009-06-23 7:17 ` Rob Weir
2009-06-23 8:31 ` Stephen J. Turnbull
2009-06-23 14:06 ` Chong Yidong
2009-06-23 18:44 ` Stephen J. Turnbull
2009-06-23 19:09 ` Dan Nicolaescu
2009-06-24 5:59 ` Stephen J. Turnbull
2009-06-24 6:18 ` Jason Rumney
2009-06-24 6:52 ` Dan Nicolaescu
2009-06-24 7:51 ` tomas
2009-06-24 14:58 ` Dan Nicolaescu [this message]
2009-06-24 22:46 ` Stephen J. Turnbull
2009-06-24 21:41 ` Stefan Monnier
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=200906241458.n5OEw9ND002207@godzilla.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.org \
--cc=tomas@tuxteam.de \
/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).