unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: chad brown <y@MIT.EDU>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Disable VC when Emacs is noninteractive -batch
Date: Wed, 15 Aug 2007 21:08:07 -0400	[thread overview]
Message-ID: <E1ILTqJ-0002U2-Em@fencepost.gnu.org> (raw)
In-Reply-To: <8EF38E17-F615-4EC1-B971-024AE0651795@MIT.EDU> (message from chad brown on Tue, 14 Aug 2007 21:14:04 -0700)

    I'm not sure that I understand your question, but maybe I can clarify  
    via example:  ~/Library/elisp/RCS/mh-flists.el,v  exists and contains  
    valuable (to me) historic information about changes over time, but ~/ 
    Library/elisp/mh-flists.el does not exist,  should not exist, and has  
    not existed for many months.

What is the motive for doing things this way?
Is it considered normal RCS usage?

Why not rename the master file
to some name that nothing will try to use,
such as ~/Library/elisp/RCS/=mh-flists.el.old,v
or ~/Library/.archive/elisp/RCS/mh-flists.el,v
?

  reply	other threads:[~2007-08-16  1:08 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-05 19:39 [PATCH] Disable VC when Emacs is noninteractive -batch Michael Olson
2007-08-05 22:06 ` Dan Nicolaescu
2007-08-06  1:32   ` Michael Olson
2007-08-06  5:20     ` Miles Bader
2007-08-06  2:36   ` Stephen J. Turnbull
2007-08-06 16:33     ` Richard Stallman
2007-08-06 18:07       ` Stephen J. Turnbull
2007-08-07  7:29         ` Richard Stallman
2007-08-07  8:59           ` Stephen J. Turnbull
2007-08-07 20:12             ` Richard Stallman
2007-08-06 20:46       ` Michael Olson
2007-08-06 21:22         ` Jason Rumney
2007-08-07  7:29         ` Richard Stallman
2007-08-07 10:18           ` David Kastrup
2007-08-07 20:12             ` Richard Stallman
2007-08-07 20:46               ` David Kastrup
2007-08-07 11:40           ` Michael Olson
2007-08-08  4:54             ` Richard Stallman
2007-08-08 13:07               ` Stefan Monnier
2007-08-08 13:29               ` Michael Olson
2007-08-09  5:23                 ` Richard Stallman
2007-08-07 15:53         ` Edward O'Connor
2007-08-06 14:19 ` Richard Stallman
2007-08-06 18:38 ` Stefan Monnier
2007-08-06 19:16   ` David Kastrup
2007-08-07  0:44     ` Miles Bader
2007-08-07  3:08     ` Eli Zaretskii
2007-08-07  6:07       ` David Kastrup
2007-08-07  6:51         ` Michael Olson
2007-08-07 20:11         ` Richard Stallman
2007-08-07 20:42           ` David Kastrup
2007-08-09  0:06             ` Richard Stallman
2007-08-09  0:17               ` David Kastrup
2007-08-11 16:38                 ` chad brown
2007-08-12 17:56                   ` Richard Stallman
2007-08-15  4:14                     ` chad brown
2007-08-16  1:08                       ` Richard Stallman [this message]
2007-08-14 15:46                   ` Davis Herring

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=E1ILTqJ-0002U2-Em@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=y@MIT.EDU \
    /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).