All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Czech <cc@derago.com>
To: mlmmj@mlmmj.org
Subject: Re: Version control systems
Date: Sat, 07 Mar 2009 17:02:58 +0000	[thread overview]
Message-ID: <49B2A8C2.4080309@derago.com> (raw)
In-Reply-To: <49B17DC7.7070600@goirand.fr>

[-- Attachment #1: Type: text/plain, Size: 2275 bytes --]

I think you have really to try hg or git, to get a feel what is different.

Personally I used rcs for one year and than personally and in company 
cvs for another 13 years until beginning 2006. Than all projects where 
switched to hg  because if several developers are involved especially 
over the internet it is more easy and efficient. I think that mozilla 
for firefox and other projects also switched to hg and other small or 
big projects to git or hg does show that they have some advantages. To 
try something out and keep this changes in your personal repo and maybe 
reuse it at a later time can be quite interesting. You just have your 
personal repo for testing, commiting etc. but not push it to main repo 
maybe at this time. It is much more flexible.

Just convert the cvs repo to hg/mercurial and use it for several weeks 
in parallel. Or maybe just go to the directory where your source is and 
enter:

hg init
hg addremove
hg commit

than you have the current source code in hg and try it for some weeks.

Another point is if you want try something and you have a central repo 
of hg you can just create a directory and enter

hg init
hg pull (with https://path to repo)
hg update
to get a working copy of the source and the repo. If your new changes 
don't work you can just delete the directory. For big tests this is 
quite nice. You just commit to your local repo. If you see that your 
ideas work you can just push them to central repo.

Maybe if you are used to use cvs this sounds complicated but first there 
is also a graphical version you don't need to use command line and 
second after a small amount of time you see that you are much more 
flexible and creative with such an approach like hg or git. I use hg 
because in the past it was more straight forward to use and the windows 
version was in par. Maybe this changed over the years so in general 
there is no big difference if you  use git or hg but cvs is really 
another world. It is not so much different to use but because of the 
centralized nature much less convenient.

It does not matter if you use it for a small or a big project. I really 
recommend just to try. Just spent 2 or 3 ours with hg and you will learn 
a lot and it is also quite interesting. So just give it a try.



[-- Attachment #2: Type: text/html, Size: 2674 bytes --]

  parent reply	other threads:[~2009-03-07 17:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-06 19:47 Version control systems Thomas Goirand
2009-03-07 13:53 ` Morten K. Poulsen
2009-03-07 14:00 ` Mads Martin Joergensen
2009-03-07 17:02 ` Christian Czech [this message]
2009-03-07 20:21 ` Thomas Goirand
2009-03-07 22:14 ` Mads Martin Joergensen
2009-03-07 23:05 ` Christian Laursen
2009-03-08  8:49 ` Thomas Goirand
2009-03-08  8:58 ` Mads Martin Joergensen

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=49B2A8C2.4080309@derago.com \
    --to=cc@derago.com \
    --cc=mlmmj@mlmmj.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.
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.