Date: Sat, 1 Oct 2016 13:18:06 +0100 From: Steve O'Hara-Smith <steve@sohara.org> To: freebsd-questions@freebsd.org Cc: Polytropon <freebsd@edvax.de> Subject: Re: cvs Message-ID: <20161001131806.4b2ecccdf5771451319bcdbb@sohara.org> In-Reply-To: <20161001095248.8d468656.freebsd@edvax.de> References: <6470061F-3127-4CD8-BB14-EB46D46B0BF1@mail.sermon-archive.info> <23c8bfcb-5112-accb-6607-3448104d5a0f@holgerdanske.com> <17E1B6D8-4BC6-4698-8E5C-7EFF7CD7E31F@mail.sermon-archive.info> <alpine.BSF.2.20.1609290653420.7457@wonkity.com> <1A870E64-1FD1-4B4F-BDD4-D104DA79D488@mail.sermon-archive.info> <0c1654bc-5398-3a88-556d-ce90e761cb44@citrin.ru> <20161001095248.8d468656.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 1 Oct 2016 09:52:48 +0200 Polytropon <freebsd@edvax.de> wrote: > Subversion almost "works the same" as CVS, even though it adds > a lot of features, so it's typically considered the "natural > successor" of CVS. Git is often said to be "too different" and > "surprising" in what its subcommands do. :-) Yep it took having to use it for me to grok git, once I did I've found it really rather good, but it is very different to CVS or SVN in approach and until you grok the way it works it is very confusing. One neat git trick - create a repository in the root of each machine you maintain, commit all changed config files to it and (here's the nice bit) clone all the repositories (ssh access) to safe storage (eg ZFS array) and run a cron job to keep the clones updated (git pull in each clone). Result painless version controlled, backed up config for all systems and jails with a local copy for mistakes and central copy for disasters. -- Steve O'Hara-Smith <steve@sohara.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161001131806.4b2ecccdf5771451319bcdbb>