[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Groff] UTP - should we use version control?
From: |
Jon Snader |
Subject: |
Re: [Groff] UTP - should we use version control? |
Date: |
Sat, 1 Feb 2003 15:08:54 -0500 |
User-agent: |
Mutt/1.4i |
On Sat, Feb 01, 2003 at 07:17:22PM +0100, Heinz-J?rgen Oertel wrote:
> I got the last version of appa.t.gz from Larry's site and it seems that I
> have
> a 'newer' (or better?) one on my PC. This remembers me that I wanted suggest
> using at lest a simple version control mechanism for the files. I use RCS on
> my PC and the files with a slightly modified Header:
>
>
> .ig
> appa.t
> Typed by: Heinz-J?rgen Oertel
> Marked up by: Heinz-J?rgen Oertel
> Proofed on: 22 Oct 2002 by Andreas K?h?ri <address@hidden>
>
> $Id: appa.t,v 1.3 2002/11/02 20:10:29 oe Exp $
> $Log: appa.t,v $
> Revision 1.3 2002/11/02 20:10:29 oe
> used .page macro and \(lq, \(rq
>
> Revision 1.2 2002/11/02 19:53:07 oe
> 1. proof reading by Andreas K?h?ri
>
> ..
>
> Each maintainer can look back on what was changed last times.
> I suggest using this simple method for all of us. Tkdiff is a very powerful
> tool to see changes to previuos versions.
>
It's probably too late in the process for this to make much difference
in the original project, but I think it's definitely a great idea for
the update. There's nothing to say, of course, that Larry (or someone
who has access to a server) couldn't set up a CVS server for the current
book, and then use that as a jumping off place for the update.
Maybe even SourceForge could be used for this. What does everyone else
think?
Jon Snader