unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: rustom <rustompmody@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Choosing a versioning system
Date: Mon, 31 Mar 2008 08:38:26 +0200	[thread overview]
Message-ID: <87hcenjt3x.fsf@gmail.com> (raw)
In-Reply-To: <7ec32e9d-eb2b-42b7-90bb-d24dbf9a4475@s19g2000prg.googlegroups.com> (rustom's message of "Sun, 30 Mar 2008 20:55:17 -0700 (PDT)")

rustom <rustompmody@gmail.com> writes:

> On Mar 30, 11:59 pm, Oleg Katsitadze <oleg...@gmail.com> wrote:
>> CVS is good but has a few flaws.  Don't use it for new projects.
>>
>> SVN (subversion) is a successor to CVS with the flaws fixed and new
>> features added.
>>
>> Distributed systems (git, monotone) are good when you don't have (or
>> don't want to have) a server to keep the repository.
>
> Yes that is my impression also.
> What your reply suggests however is that we are seeing a cycle of
> simple-complex-simple:
> rcs -- simple (no server)
> cvs,svn -- more complex because needs centralized server
> modern distributed ones -- once again no need for server but with the
> lock model replaced with the merge model (see
> http://svnbook.red-bean.com/en/1.2/svn.basic.vsn-models.html )
>
> And so I was wondering if these systems give the best of all worlds?
>
> But... there are just too many to choose from!!  bzr, darcs, git,
> mercurial, monotone...
> [Alphabetically listed  :-)   ]
>
> So my question is: For people living much of their lives in emacs and
> among other things trying to keep their own stuff versioned, what do
> you use??
>
> For the choice rcs-for-sysadmin files I see 3 options:
>
> -- make the ,v file next to the original file
> -- make the ,v file in an RCS directory  -- but that way one could end
> up having tens (100s?) of RCS directories in /etc alone!
> -- there is some way (I dont know of) of making one RCS repo for all
> files or at least all sysadmin file. So that something like 'I keep my
> home in svn' http://kitenet.net/~joey/svnhome/ is possible with RCS
>
RCS do one directory RCS by directory.
thats mean that for /etc for example you will have one directory RCS for all the
files you have under version in this directory.
If you register a file in a subdirectory of /etc you will have a RCS directory in
this subdirectory ....etc..
If you use RCS for file in /etc think at unlocking the files that can be dynamically
modified by the system.
But another time, if you want to put under version a big set of files like /etc,
use another version system.
CVS ==> bof...
SVN ==> good but a central repository.
mercurial ==> very good, own repo, you can use it with dvc.
git ==> seem to be the more advanced, work with dvc.
bzr ==> seem good, never tried, work with dvc.

With mercurial, if you want to put under version all /etc,
just do while you have cd in /etc:
hg init.==> thats done, all files in /etc and all subdir are under version!
-- 
A + Thierry
Pub key: http://pgp.mit.edu




  reply	other threads:[~2008-03-31  6:38 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28  7:30 My dream work log: Albert
2008-03-28 16:50 ` B. T. Raven
2008-03-29 17:18   ` Mike Treseler
2008-03-30 17:21     ` Choosing a versioning system (was My dream work log:) rustom
2008-03-30 17:50       ` Choosing a versioning system Thierry Volpiatto
2008-03-30 18:32       ` Choosing a versioning system (was My dream work log:) Mike Treseler
2008-03-31 19:06         ` Choosing a versioning system Joel J. Adamson
     [not found]         ` <mailman.9728.1206990435.18990.help-gnu-emacs@gnu.org>
2008-03-31 20:24           ` Mike Treseler
2008-03-30 18:59       ` Choosing a versioning system (was My dream work log:) Oleg Katsitadze
     [not found]       ` <mailman.9661.1206909269.18990.help-gnu-emacs@gnu.org>
2008-03-31  3:55         ` rustom
2008-03-31  6:38           ` Thierry Volpiatto [this message]
2008-03-31 21:06             ` Choosing a versioning system Mike Mattie
2008-04-03 18:25               ` Nikolaj Schumacher
2008-04-03 18:51                 ` Thierry Volpiatto
2008-04-04 16:41                   ` Nikolaj Schumacher
2008-04-04 17:46                     ` Thierry Volpiatto
2008-03-31  8:22       ` Tim X
2008-03-31 22:23         ` Timothy Hobbs
2008-04-01 15:37           ` Automatic versioning (was: Choosing a versioning system) Joel J. Adamson
2008-04-01 20:48             ` Automatic versioning Timothy Hobbs
2008-04-02 13:39               ` Joel J. Adamson
2008-04-03  2:00               ` Kevin Rodgers
2008-04-03  5:22                 ` Timothy Hobbs
2008-04-04 12:24                   ` Kevin Rodgers
2008-04-04 13:44                     ` Joel J. Adamson
2008-04-04 20:35                     ` Timothy Hobbs
2008-04-05  0:00                       ` Xavier Maillard
2008-04-05  4:21                         ` Timothy Hobbs
2008-04-03 14:18                 ` Joel J. Adamson
2008-04-04 12:28                   ` Kevin Rodgers
2008-03-31 19:04       ` Choosing a versioning system Joel J. Adamson
2008-03-28 17:03 ` My dream work log: Thierry Volpiatto
     [not found] ` <mailman.9546.1206722977.18990.help-gnu-emacs@gnu.org>
2008-03-29  8:36   ` Albert

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=87hcenjt3x.fsf@gmail.com \
    --to=thierry.volpiatto@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=rustompmody@gmail.com \
    /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).