unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: RCS and Emacs, between machines.
Date: Fri, 27 Sep 2002 19:23:40 +0200	[thread overview]
Message-ID: <vafk7l7uz1f.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: vflm5nxw62.fsf@rpc71.cs.man.ac.uk

Phillip Lord <p.lord@russet.org.uk> writes:

> Anyone else do similar things? [work on files with version control
> in more than one location] Anyone got a good solution?

I use CVS and ssh to connect to the repository.  But it seems you
don't have an internet connection from home, so this is not a good
choice.

But maybe your problem is that while working at home you'd like to
store several versions?  That can be done with the new, nifty,
changing backends feature of VC.  When working on a file in a CVS
working directory, you can do C-x v b to switch to the RCS backend.
Then you can store several versions at home.

But when you switch back to CVS as the backend, there is no easy way
to upload all those RCS revisions in one go.  When you do a CVS
checkin, just the most recent version is uploaded so that the CVS
repository doesn't know about the intermediate versions.

Another possibility is to make sure that the RCS files are always
unlocked, by doing "ci -u" on them before putting them on the floppy.

Yet _another_ possibility is to store the CVS repository on the
floppy, too.

And then, you can do "rcs -U" on the files; maybe that helps.

kai
-- 
~/.signature is: umop ap!sdn    (Frank Nobis)

      parent reply	other threads:[~2002-09-27 17:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-27 15:57 RCS and Emacs, between machines Phillip Lord
2002-09-27 16:09 ` Holger Sparr
2002-09-30  9:11   ` Phillip Lord
2002-09-27 16:15 ` Alan Shutko
2002-09-30  9:12   ` Phillip Lord
2002-09-30 13:38     ` Alan Shutko
2002-09-30 14:58       ` Phillip Lord
2002-10-04  7:21         ` Lee Sau Dan
2002-09-27 17:23 ` Kai Großjohann [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=vafk7l7uz1f.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.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.
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).