Mail Archives: geda-user/2013/01/15/10:41:43

X-Authentication-Warning: 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;; s=20120113;
X-Received: by with SMTP id b14mr30452444vdt.0.1358264492769;
Tue, 15 Jan 2013 07:41:32 -0800 (PST)
From: Ben Gamari <bgamari DOT foss AT gmail DOT com>
To: Ouabache Designworks <z3qmtr45 AT gmail DOT com>, geda-user AT delorie DOT com
Subject: Re: [geda-user] geda-skeleton-project: Lowering the cost of a starting a gEDA project
In-Reply-To: <>
References: <87wqvhd4tw DOT fsf AT gmail DOT com> <kd21ao$j6j$1 AT ger DOT gmane DOT org> <20130115013756 DOT 9917 DOT qmail AT stuge DOT se> <CAOP4iL0yLZ-gvovCy5zCmJyjOXUUaoOB5U1+6CqcD20BM15FiQ AT mail DOT gmail DOT com> <50F4E4D1 DOT 3010802 AT ecosensory DOT com> <CAOP4iL1f=3TV5UKUjyJtpUw_5oBDxpk=5S2F=dEcUC2UYiNhVQ AT mail DOT gmail DOT com>
User-Agent: Notmuch/0.14+240~g0ab5e9f ( Emacs/23.4.1 (x86_64-pc-linux-gnu)
Date: Tue, 15 Jan 2013 10:41:30 -0500
Message-ID: <>
MIME-Version: 1.0
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

Ouabache Designworks <z3qmtr45 AT gmail DOT com> writes:

> On Mon, Jan 14, 2013 at 9:10 PM, John Griessen <john AT ecosensory DOT com> wrote:
>> So that simplifies using your libraries, but what about keeping a snapshot
>> of the
>> symbols and footprints as they were the day that project completed a
>> version and made
>> fab data?  It sounds like you are suggesting having your project dir not
>> under a revision control system.
> You can keep all of that but just don't try and put it in the same
> repository as the source design data. When you release a design you copy
> to something like frobozz_pca_12_jan2013_release and that will contain all
> the source and generated files used in the release. Save that because you
> might need it
> someday if there are issues.
This is what version control systems are for. Tags and branches exist
precisely for this reason. In the case of git, one can handle the case
of multiple source repositories with git-submodule. Other modern VCSes
have similar facilities. There are much better tools than cp(1) for
dealing with archival and versioning.


- Ben

- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019