Date: Sun, 29 Mar 2009 07:37:27 -0400 From: Glen Barber <glen.j.barber@gmail.com> To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: [OT] - Best Practices(TM) for Configuration File Changes Message-ID: <4ad871310903290437q269964d7k54a449f405fb31b2@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hello, list. Before I pose my question, I am not intending to start a flame-war of any sort -- I'm just searching for "different" ways of doing things. With so many different version control systems available (aside from the traditional "keep current backups" solution), I am curious: Q: What is *your* favorite/suggestion solution to keep (working) versions of configuration files, in case something goes awry? I am specifically targeting configuration files because they are what I change the most, in avoidance of "It worked 10 minutes ago..." situations. Cheers, -- Glen Barber
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ad871310903290437q269964d7k54a449f405fb31b2>