all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Barry OReilly <gundaetiapo@gmail.com>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Switching branches and TAB
Date: Fri, 31 May 2013 11:41:03 -0400	[thread overview]
Message-ID: <CAFM41H0qZs131N9CTRtFmXQFB0hfrgew+eTTYDaN2Q++owaS2A@mail.gmail.com> (raw)

> At the moment, I have 18 views active (each in its own xterm) with
> 12 instances of Emacs running (not running Emacs in 6 views).

I use snapshot views for the improved local filesystem IO. Also so as
timestamps don't move backwards for uncheckouts and some config spec
changes, which leads to incorrect builds for timestamp based build
systems.

Snapshot views allow a source tree for each discrete task like many
other VCSes. I use a "current" symlink to the source tree of primary
interest. If the symlink is changed, Emacs auto revert loads the new
current source tree. I also open Emacs in "non current" source trees
for secondary tasks.

> http://www.emacswiki.org/emacs/ClearCase

I tried clearcase.el but according to my notes it slowed down
initialization too much. What's useful to me is to define one command
for checking out and do the other cleartool commands from the shell.

  (lambda ()
    (interactive)
    (call-process "cleartool"
                  nil nil nil
                  "co" "-nc"
                  (buffer-file-name))
    ;; Get the new write permissions
    (revert-buffer))

> I find ClearCase more powerful than most other source code
> management systems.

I'm baffled anyone experienced with ClearCase and at least one modern
VCS could reach that conclusion.


             reply	other threads:[~2013-05-31 15:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-31 15:41 Barry OReilly [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-05-30 19:47 Switching branches and TAB Barry OReilly
2013-05-30 22:59 ` Ludwig, Mark
2013-05-30 15:57 berk.dev
2013-05-31  5:14 ` Kevin Rodgers

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFM41H0qZs131N9CTRtFmXQFB0hfrgew+eTTYDaN2Q++owaS2A@mail.gmail.com \
    --to=gundaetiapo@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.