X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Spam-Checker-Version:	SpamAssassin 3.3.2 (2011-06-06) on fly.srk.fer.hr
X-Spam-Level:
X-Spam-Status:	No, score=-1.0 required=6.3 tests=ALL_TRUSTED
	autolearn=disabled version=3.3.2
Date:	Wed, 18 Mar 2015 18:51:53 +0100
From:	Ivan Stankovic <pokemon AT fly DOT srk DOT fer DOT hr>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] pcb alternatives
Message-ID:	<20150318175153.GA2782@alpha2>
References:	<5508413E DOT 4000405 AT ecosensory DOT com>
	<46050a0c DOT 619 DOT 14c2850d052 DOT Webtop DOT 45 AT optonline DOT net>
	<CAGYR9veihi_M+B0HXptGYQLMO8=B_KOLM2wmrRNkMLG_9MdQrA AT mail DOT gmail DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1503180357520 DOT 25799 AT igor2priv>
	<CAGYR9ve_n7VmZ8x-jCQK5eKHMNGp6an9o8EwYZnWQWFiCpGnXg AT mail DOT gmail DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1503180827170 DOT 25799 AT igor2priv>
	<CAC4O8c--CeEiKjxCKrs38XGjOyPS0Cy6scZ5HsAFgpi5xDpP_w AT mail DOT gmail DOT com>
	<201503181619 DOT t2IGJkZD012945 AT envy DOT delorie DOT com>
	<AC2776EE-AD74-4AC9-BCB1-9F40CC439B5D AT noqsi DOT com>
	<CAOuGh8-FeFY9SMm6kHtaXCHdgchGuLS8LFsPj1Ud=Tx+XnuiiA AT mail DOT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<CAOuGh8-FeFY9SMm6kHtaXCHdgchGuLS8LFsPj1Ud=Tx+XnuiiA@mail.gmail.com>
X-Operating-System:	GNU/Linux
User-Agent:	Mutt/1.5.23 (2014-03-12)
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id t2IHosFu020636
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Wed, Mar 18, 2015 at 01:07:25PM -0400, Bob Paddock wrote:
> > Well, of course, that’s a matter of trying to do manually what git does automatically. The commit messages are your changelog in git.
> 
> While this does not in way apply to gEDA and company,
>  any VCS that lets history be rewritten is a show stopper in many
> regulatory/military development environments.

This kind of argument often comes from a "security theater" perspective.
In reality, there are many ways for important data to become unavailable
or useless, regardless of the regulations that had been put in place to
prevent it.

For git, or any other VCS that supports history rewriting, there
are mechanisms that allow you to disable history rewriting and they
work quite nicely.

We use git at work and routinely rewrite history in our local repos.
Sometimes (very rarely, though) it happens that the history is
rewritten on the "central" repo.

-- 
Ivan Stankovic, pokemon AT fly DOT srk DOT fer DOT hr

"Protect your digital freedom and privacy, eliminate DRM, 
learn more at http://www.defectivebydesign.org/what_is_drm"

- Raw text -