X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=date:from:to:subject:message-id:mail-followup-to:references
         :mime-version:content-type:content-disposition:in-reply-to
         :user-agent;
        bh=ML6VAHtUS3cBiG9V+iNLnuubDPMzrYLxcox1KOzccqs=;
        b=ORb0P9+gxpSJHd/4yKu0jPRJYTJwlPUhQLEz3kE+4zyZh58WcWvEKRzLiMpMRY078A
         zBCM2xY9H6blsPE3ryx6T368ixQFyvk95mpdIW+rYcfxLx7k7RlvxQZStyCoWMwmZ7tU
         330jykNyFEdkez3cG/djv1T9FRW9vgsW6rupYXMGoNsWAgzejuQNWP3NZF5v3RrjY65F
         2SnlGRzhxvWYJ9iAgTGMeaDsojjhByUWIW6tDHwOb9209mGZqwir0kOiLs/xn8/QOqwm
         rR3RZSB9xHjryLFukBwbixJ9MhiJcvTs5uk9TDLxOIQm9cky78Q8MaL0ugiTCGReM7W0
         LHAQ==
X-Received: by 10.152.28.233 with SMTP id e9mr3195423lah.3.1427193996300;
        Tue, 24 Mar 2015 03:46:36 -0700 (PDT)
Date: Tue, 24 Mar 2015 13:46:34 +0300
From: Vladimir Zhbanov <vzhbanov AT gmail DOT com>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] gschem edits vanishing
Message-ID: <20150324104634.GB25693@localhost.localdomain>
Mail-Followup-To: geda-user AT delorie DOT com
References: <550D5F43 DOT 7020501 AT earthlink DOT net>
 <1427055675 DOT 10088 DOT 11 DOT camel AT cam DOT ac DOT uk>
 <20150323185439 DOT GA2429 AT localhost DOT localdomain>
 <5510D488 DOT 3070309 AT earthlink DOT net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <5510D488.3070309@earthlink.net>
User-Agent: Mutt/1.5.23 (2014-03-12)
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
Precedence: bulk

On Mon, Mar 23, 2015 at 10:05:44PM -0500, David W. Schultz wrote:
> On 03/23/2015 01:54 PM, Vladimir Zhbanov wrote:
> > ... and using a CMS helps to avoid such mistakes.
> > 
> 
> Once it reaches the point where I am ready to get boards fabbed, I will
> use git for version control. But that wouldn't help here because at this
> point there is only the one copy. Unless you count that tarball thing
> that the backup program produced that lives on storage media that is
> only ever connected when I am doing a backup.
It would help because
  - you always can see uncommitted changes
  - you can revert any unwanted change even if you've committed it
  - every time you can see what difference was introduced using
    graphical diff

Cheers,
  Vladimir