unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
Cc: Juanma Barranquero <jmbarranquero@wke.es>,
	emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
	Miles Bader <miles@gnu.org>
Subject: Re: Wheter to switch to another VC, and which one...
Date: Wed, 24 Mar 2004 05:24:18 -0500	[thread overview]
Message-ID: <20040324102413.GA32548@fencepost> (raw)
In-Reply-To: <m3y8pq8qkt.fsf@kfs-l.imdomain.dk>

On Wed, Mar 24, 2004 at 11:52:34AM +0100, Kim F. Storm wrote:
> > > We have discussed moving quite a lot of the lisp files around, and
> > > doing that under Subversion (which keep history across moves) would be
> > > a big win compared to CVS.
> > 
> > Arch too (of course).
> 
> Does it keep the history on the moved/renamed file as well?
> 
> Ah, yes, I suppose arch can do that with the arch tag on each file.

The thing to remember is that arch doesn't keep per-file history _at all_ --
log files are associated with changesets.

In many cases, this is actually more useful than a per-file history, but
sometimes you do want to see that.  As it turns out, there's enough
information kept in the changeset logs that you can easily (and
automatically) track a file's evolution through a series of changesets.

I have a shell script (`tla-file-log') that does this and emits cvs-style log
output.  However, in practice I find I rarely use it; more often I just want
to see the overall branch history.

-Miles
-- 
"I distrust a research person who is always obviously busy on a task."
   --Robert Frosch, VP, GM Research

  reply	other threads:[~2004-03-24 10:24 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23  6:46 deleting rcs keywords from emacs sources Miles Bader
2004-03-23  7:47 ` Eli Zaretskii
2004-03-23 10:56   ` Kim F. Storm
2004-03-23  9:51 ` spiegel
2004-03-23 10:16   ` Miles Bader
2004-03-23 11:41   ` Juanma Barranquero
2004-03-23 13:13     ` Miles Bader
2004-03-23 14:01       ` Juanma Barranquero
2004-03-23 14:35         ` Miles Bader
2004-03-23 14:58           ` Juanma Barranquero
2004-03-23 15:14             ` Stefan Monnier
2004-03-23 15:36               ` Juanma Barranquero
2004-03-23 23:38                 ` deleting rcs " David Kastrup
2004-03-24  5:34             ` deleting rcs keywords " Richard Stallman
2004-03-23 15:04         ` Stefan Monnier
2004-03-23 15:39           ` Wheter to switch to another VC, and which one Juanma Barranquero
2004-03-23 16:25             ` Stefan Monnier
2004-03-23 16:43               ` Masatake YAMATO
2004-03-23 17:17                 ` Stefan Monnier
2004-03-23 17:31                   ` Masatake YAMATO
2004-03-23 18:50                     ` Stefan Monnier
2004-03-24  0:17             ` Kim F. Storm
2004-03-23 23:35               ` Miles Bader
2004-03-24 10:52                 ` Kim F. Storm
2004-03-24 10:24                   ` Miles Bader [this message]
2004-03-24 17:48               ` Stefan Monnier
2004-03-23 18:17       ` deleting rcs keywords from emacs sources Nick Roberts
2004-03-23 18:07     ` Nick Roberts
2004-03-24  5:34 ` Richard Stallman
2004-03-25  8:17   ` Miles Bader

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=20040324102413.GA32548@fencepost \
    --to=miles@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jmbarranquero@wke.es \
    --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).